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?
- 2 Answers
- 4549 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
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 |
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 |
can any one send me all the interview point of view questions from manual testing please..........
Did you ever worked with B.A's and when?
What is Defect Density? How it can be calculated?
1.when do we start testing and explain briefly please assp 2.when will we stop testing friends tell me immediatly
1) How to test session ? 2) There is a website in which the user has to register to use its features. Suppose one user has registered in that site by paying some amount only for 1 month. Now i want to test the application that the user should not use the features of the site after 1 month. How to test it? The tester cannot wait for 30 days to test it....bear in mind..Thanks in advance...
On what basis you are fixing up the time for project completion?
what is exit criteria for testing?
Can Anybody give simple example for High seveority , low priority and High Priority low sevority defect or bug..Thanks in advance......
what is testing
is there any checklist to check SRS document
which document we prepare first whether test plan or test case document
What are the different types of integration testing?
Automation Testing 
