Tuesday, December 22, 2009

Whenever a fault is detected and fixed then the software should be re-tested to ensure that the original fault has been successfully removed. You should also consider testing for similar and related faults.

Tests should be repeatable, to allow re-testing / regression testing.

Regression testing attempts to verify that modifications have not caused unintended adverse side effects in the unchanged software (regression faults) and that the modified system still meets its requirements. It is performed whenever the software, or its environment, is changed.

Regression test suites are run many times and generally evolve slowly, so regression testing is ideal for automation. If automation is not possible or the regression test suite is very large then it may be necessary to prune the test suite. You may drop repetitive tests, reduce the number of tests on fixed faults, combine test cases, designate some tests for periodic testing, etc. A subset of the regression test suite may also be used to verify.

3 Comments:

At December 22, 2009 at 11:10 PM , Blogger Toon India said...

nice blog..very informative
keep the posts coming!!

 
At January 2, 2010 at 7:02 AM , Blogger Rahul said...

Hi,

This Software Testing artical is very useful for me. I am a QA Engineer and always

looking to learn something new. I would like to introduce another good Software Testing

blog, Have a look.

http://SoftwareTestingNet.com

 
At January 5, 2010 at 7:35 AM , Blogger QualityPoint said...

Hi,

First of all Thanks very much for your useful post.
This Software Testing article is very useful for me. I would like to introduce another good
blog which is having free software testing ebooks and technical content, Have a look.
http://qualitypoint.blogspot.com/2009/12/released-two-ebooks-for-learning.html

 

Post a Comment

Subscribe to Post Comments [Atom]

Links to this post:

Create a Link

<< Home