Pete Becker wrote:
Ian Collins wrote:
Pete Becker wrote:
As I said, "regression test" has come to mean "test." Too bad.
Is arguably more accurate to say that "regression test" has come to mean
"acceptance test".
Well, back in the day, we had unit tests, integration tests,
acceptance tests, and regression tests.
One role of all test is to prevent regressions.
Yes, and that is apparently taken to mean that every test is a
regression test.
Regression test is running tests from previous versions that still apply
(ie are not being changed in the current iteration). In other words,
you have a product that parses XML. It's old and doesn't do schema. You
decide to add that feature. You build acceptance and integration tests
that test your new feature. You also want to make sure that it still
parses all the stuff it did before so your run a _regression_suite_ at
times additional to your new tests. It may be that you do them both
every time but then again you might have a lot of old features so maybe
you want to speed things up a bit by skipping the regression and only
running it once a night.
Tests from previous versions that still apply test current requirements.
Roundhouse Consulting, Ltd. (www.versatilecoding.com)