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

On what basis we will perpare test data...?

5 Answers  


what is version 1

11 Answers  


i have an iphone 4g can you tell me the test case for the camera?

8 Answers  


Diff b/w test case and test script?

1 Answers   Crea,


What Questions Project Manager will be aske?

2 Answers  






Hi frnds can any one tel me , "How can we do security testing while testing a project" ?pls reply soon correct answer ?

1 Answers  


how do u develop test harness?

5 Answers   Semantic Space,


what is meant by test strategy?

2 Answers  


How the Error, Defect and Bug are related to each other ?.

12 Answers   FIC, Vinfotech,


what is test plan and test stategy and also differnce bet them?

5 Answers   RealPage,


explain the 5 types test matrics?

1 Answers   Persistent,


How to prepare traceability matrix?

1 Answers  


Categories