What is Tacebility Matrix What are the Columns it contains
Answers were Sorted based on User's Feedback
Answer / v ramesh babu
Tracebility Matrix is document that mapping the test cases
with requirements.
there are five columns are there in Tracebility Matrix.
Requirement Id
Function specification Id
Design Id
Soure Code
Test Cases ( Give the test case start and end number)
Is This Answer Correct ? | 2 Yes | 0 No |
Answer / sm
Traceability matrix is very essential at the time of
identifying test coverage.
It will give mapping in between Test cases with customer
requirements along with test case defect status.
Columns in the Traceability matrix:
Requirement id
Requirement description
Test case Id
Test case Description
Test status
Defect status
Covered status
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / ram mohan
TM : it is a maping b/w test cases and requirments
columna of TM are
1. requirment ID
2. requirment Description
3. Design Doc. ID
4. Coading ID
5. unit testing TC ID
6. Integration Testing TC ID
7. System Testing TC ID
8. Acceptance Testing TC ID
Is This Answer Correct ? | 0 Yes | 1 No |
What is your experience with change control? Our development team has only 10 members. Do you think managing change is such a big deal for us?
diff b/w test case and test script?
how you get build from developer? pl answer it?wht is build ?
What exactly is quality control? Is it similar to quality assurance?
How does quality control differ from quality assurance?
i have done B.E. computer in 2009 i have done software testing course and also 6 months exp in testing on live project as trainee, now a days i am searching job in pune. can any one tell me any opening in pune?
What is meant by UAT testing? And how is the UAT testing carried out?
fields present in bugs and fields present in testcases? pl pl pl give me an answer thanks in advance but pl.
you r a tester having good knowledge of coding.now in ur company developers are having some problem in coding will u (tester) help them.
What is Entry and Exit Criteria? When and how we will consider them? Can any one explain this Question.
While doing system testing your have missed out some issues. The same issue is found by customer and he reverts back to you for an explaination. How do you convince him or how do you justify yourself about your testing?
What types of documentation are used in qa?