I m writting the test cases in Excel sheet. After wrting
test cases for version 2.0.0
If there is new feature added in build 2.0.1, I will write
test cases for newly added feature.
Then 3.0 version release for testing with new feature. I
will write test cases for newly added feature 3.0
But if in between 2.0.2 build release for testing with same
feature of 3.0.Then should I have to write test cases for
same feature again?
If not --> when 2.0.2build again release for testing after
2months then How should I came to know that I have to run
these test cases on 2.0.2build?

Answers were Sorted based on User's Feedback



I m writting the test cases in Excel sheet. After wrting test cases for version 2.0.0 If there is..

Answer / imthiyaz. shaik

If I understood your question correctly, Tracebility matrix
is the solution.

Tracebility matrix maps the test cases with the
requirements so that no requirement is missed out.

In case of any new requirement, add the new requirement to
the Tracebility matrix and write a new test case thats maps
the new requirement.

Well managed Tracebility matrix will let you know what test
cases needs to be tested as per the features added or new
requirement.

Regards,
Imthiyaz. Shaik

Is This Answer Correct ?    2 Yes 0 No

I m writting the test cases in Excel sheet. After wrting test cases for version 2.0.0 If there is..

Answer / koteswara rao.k

I got your critical question and valid real time one .
Sol : suppose you write the test cases for the version 6
then few days after need to write the new fuctionality 6.1
in such case you should tagged the new version tcs while
you were working on excel and check that duplicates will
not occur and after few days you get major related new
functionality name 6.2 .
In such case simply keep all the tcs of the previous one
and new version tcs with tags ( this will helpful even
while in track ) .
Here major understanding is when ever any modification
happen on requirements Duplicates will not follow and new
version commits the old version Major functionality .

Traceability matrix is fine but when a new defect happen we
can identify the duplicates .
If you want try a simple trial major scenario .
As a tester should be ready to run in all the
circumstances .

Any concerns /help koteswara.9.rao@gmail.com

Is This Answer Correct ?    0 Yes 1 No

Post New Answer

More Manual Testing Interview Questions

do you write test case for smoke testing?If not why?

2 Answers  


design a black box test suite for a program that accepts two strings and checks if the first string is a substring of the second string and displays the number of times the first string occurs in the second string.

1 Answers   DOEACC, PSIT,


Expain Equivalence Class Partion with an Example?

5 Answers   McAfee,


what is configuration testing

1 Answers   Ness Technologies,


Why we have to do manual testing?

0 Answers  






Iam new to Testing Field.How do i need to answer if they ask like Integaration Testing? Can you give example with your requirement?

5 Answers  


Can you explain process areas in cmmi?

0 Answers  


what is incosistent testing

0 Answers   Ordain Solutions,


write testcases for open dialogbox

0 Answers  


What is the difference between re testing and regression testing?

4 Answers  


write scenario to check the security of below mentioned URL? www.xyzbank.com/welcomescreen/entry?

2 Answers  


1)what are techniques used for writing the Test case?

5 Answers  


Categories