Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
56 views1 page

Regression Testing: Means Executing The Same Test Cases On The Modified Build

Regression testing involves re-running the same test cases after changes to ensure previous functionality was not affected. There are two types of regression testing: bug regression testing which re-tests previously failed cases to check if bugs were fixed, and functional regression testing which re-tests past passing cases. An example process is described where 1000 test cases are run initially, with 100 failing and 900 passing. After a fix, bug regression testing re-runs the 100 failed cases and functional regression testing re-runs the 900 past passing cases.

Uploaded by

pry_kum
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
56 views1 page

Regression Testing: Means Executing The Same Test Cases On The Modified Build

Regression testing involves re-running the same test cases after changes to ensure previous functionality was not affected. There are two types of regression testing: bug regression testing which re-tests previously failed cases to check if bugs were fixed, and functional regression testing which re-tests past passing cases. An example process is described where 1000 test cases are run initially, with 100 failing and 900 passing. After a fix, bug regression testing re-runs the 100 failed cases and functional regression testing re-runs the 900 past passing cases.

Uploaded by

pry_kum
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Regression testing: means executing the same test cases on the modified build.

Like I mean which is already tested when ever the changes are made or some new functionalities
are add make sure that changes are not effected the previous functionality.
Regression testing are two types
Bug regression testing
Functional regression testing
For e.g.
If there are 1000 test cases to be executed in the first build....And of the 1000 test cases, 100 fail
and 900 pass....
suppose in 1000 test cases 3rd ,7th ,12th , 20th ..... like that upto 100 test cases are failed
initially while we are executing the test cases(1000) the 3 rd test case has failed then we will
conduct retesting on that for clarification whether it is bug or not? Before sending the bug report
with the status of 'new' And the same way we will conduct retesting on the remaining failed test
cases like 7th , 12th , 20th .....
Then after bug fixing whenever the modified build(2nd build) is received, Functional
REGRESSION Testing has to be done on the 900 test cases and the remaining 100 failed test
cases are to be Bug Regression testing. Suppose in that 3 rd one has failed once again then we
will do retesting for clarification whether it has been fixed or not? if it is not fixed before
sending the bug with the status of 're-open' and bug regression testing on 100 testcases and
functional regresssion testing on 900 test cases and on overall 1000 test cases we will
conducting regression testing.

You might also like