1 )if you have 1000 test cases ,you find out one defect in
second build that time which testing you are using
Regression Testing or Retesting ? explain with detail as
well as you want to execute all the test cases?
Answers were Sorted based on User's Feedback
Answer / nikita
we will perform regression testing to check whether the
fixed bug is not affecting the existing functionality
|Is This Answer Correct ?||5 Yes||0 No|
Answer / chandra sekhar
Regression testing only.
Basically retesting is used to test the application again
and again with different data to know the functionlaty of
the apllication with diffrent typed of data.
Where as Regression is used to revalidate whether the
defect found in the phase 1 OR 2 is resolved properly and
mainly now/currently the latest build is working fine or
not and also because of resolving the existing issues is
there any side effects/new defects created(Looking for the
new defects because of esolving the existing defect)
|Is This Answer Correct ?||6 Yes||3 No|
Answer / prateek
Retesting is carried out to ensure solution(fix) provided
by developer to defect is working correctly. Retest can be
performed with range of data.
Where as Regression testing carried out to test if fix
provided to 'defect' is not affecting existing working
functionality... Regression script(Test caese) can be a
part of your "1000 test cases" or seperate one...
Just consider out of 1000 test cases, you have run 200 test
cases & at 201 test case you found the bug... raised
defect... solution received(defect fixed by developer)...
assigned for retest...
Here you will retest the defect with range of data. If it
pass successfully then and then only you will have to think
about impact of this defect on tested & working
functionality for which you had successfully run 200 test
Pick few script from those 200 script & re execute them
again to ensure that fix is not affected any other
functionality & all are working fine...
|Is This Answer Correct ?||3 Yes||0 No|
Answer / a tester
There is bit difference between retesting and regression testing.
In Retesting, a tester tests the fix of the defect. In that tester only assure that whether that defect is fixed or not? but Regression testing carried out to test if fix
provided to that 'defect' is not affecting existing working
functionality or breaking any existing functionality.
And if a tester has 1000 test cases and have a limited time period to do the regression, tester should regress the critical functionality of the application, so business should not be impacted.
|Is This Answer Correct ?||2 Yes||0 No|
Answer / suvendu acharya
Normally we have a set of testcase which we r using for
regretion testing, we r not testing all the testcase in
each release, we r just executint the regression testcase
only to check wheather the change in one module affects the
other modules or not, so in ur case if it comes under ur
regression testcase then u have to do regression testing,
but u r saying it is a bug then as of my knowledge u have
to do retesting.
In retesting normally we r testing the diffect again and
again with same test data & test enviornment.
|Is This Answer Correct ?||0 Yes||0 No|
WE perform regression testing but not on all the test cases.
we will check with traceability matrix and based on the
requirement mapped in the traceability matrix we perform
regression on those test cases.
In traceability matrix requirement id, description and test
cases will be mentioned so we can easily map the requirement
and come to know those test cases which have to be regressed.
|Is This Answer Correct ?||1 Yes||2 No|
What are all the basic elements in a defect report?
Hello Frnds Could U plz tell me What r the contents present in TEST DIRECTOR(According to the Interview) ???
Suppose there are three modules A-B-C, the output of A is responsible for B and output of B is responsible for C and if A & C is not ready & B module is ready then how can u check Module B
what is Persistent Testing.
wht is the use of check list?
How will you select the regression test case?
For Change Password functionality-- Test Case is -- > Change Password Test Steps/Descriptions: 1) Enter Old Password 2) Enter New Password 3) Enter Confirm Password 4) Click on Save button Expected -- > User should login successfully. My question is --> After 4th step tester will check/verify that user [whose password has been changed] is login successfully or not. Should I have to write that steps which user will fallow to verify user login in above test case? What are the preconditions for above test case?
what type of questions they asked in symphony company for manual testing?
What's the difference between Load and Stress testing ?
What is Tacebility Matrix What are the Columns it contains
If any bug is found in exploratory testing, then may I consider it as a test case?
what is Gui testing and how is it performed