Answer Posted / rajendra

Traceability Matrix:

This maps the requiremnts to Testcases

In SRS Document, for every requirement there will be a
Requirement ID.

Using this Requirement ID we can identify the requirement
in the SRS document.

For example
Some Project Has 300 requirements

The requirements ID will be as follows:

R 1.0
R 2.0
R 3.0
.
.
.
.
.
.
R 300.0

Again every requirement may be composed with some fair
number of sub-requirements.

Sub Requiremnts ID will be as follows:

R 1.0 Main requirement-1
R 1.1 Sub-requirement-1 of Main requirement-1
R 1.2.... Sub-requirement-1 of Main requirement-1
.....

I think this explanation is enough about Requirement ID

Traceability Matrix looks like this
---------------------------------------------------------
RequirementID | FunctionalTestCaseID | GUITestCaseID
----------------------------------------------------------
R 1.0 FTC1,FTC2,FTC3 GTC1,GTC2,GTC3

R 1.1 FTC4,FTC5,FTC6 GTC4,GTC5,GTC6

R 1.2 No Test Case ID's

...............Etc

Like this All requirements ID will be mapped to Prepared
Test Case IDs'

For Example Look At Requirement ID R1.2 There is no
Functional Testcase ID present under the Functional
Testcase ID Column.

This says That we are not prepared the testcases For the
Requirement ID R 1.2

If we are not prepared testcases for R 1.2 we won't test
the related functionality.

This area may have some critical bugs.

So Traceability Matrix will tell the coverage of Testing.

Even in the Regression Testing If some functionality
is not working well or it has some bugs we will post the
bug to development team.

Development team will fix and Gives the new build.
This defect fixing information will contains the Build
release note.

Now using Trtaceability matrix we can identify the
Requirements which have bug fixes and Related
functionalities.

So we will repeat these Functionalities related testcases
in regression Testing.

In this way we will use the traceability matrix in
regression tetsing.

Byee

Rajendra prasade Reddy

There is only requirements document. You have 10 days and 8 resources to release the system.At the end of the 8th day u tell ur TL that system is ready for release. How will you proceed with the testing process or in other words what all approach you will follow once you get requirements

2094

---

aplitue questions will be based on wich type ?

2476

---

9.Data – driver automation typically includes?

3343

---

What are the advantages of automation over manual testing?

1131

---

What types of testing is specifically important for web testing?

1136

---

what is date field test case

1924

---

1.What is configuration Management? 2. Explain Impact Analysis 3. Explain Peer Review 4. what i kickoff phase of Formal Review. 5. Whatv are the phases of fundamental test process. 6. what is state transition testing. 7. what is LCSAJ 8. Test conditions are derived from where?

1957

---

1.Acceptance testing involves procedures for identifying acceptance criteria for interim life cycle products and for accepting them.is that? 2.Acceptance testing occurs only at the end point of the development process; it should be an ongoing activity that test both interim and final products.is it?

2371

---

What is the limit for test steps?It should be 10/20/30etc

1921

---

i have 2.5 years of experience in manual testing and qtp. can anyone say me what kind of questions do they ask on manual testing and qtp.

3464

---

How do you perform configuration management with typical revision control systems?

2127

---

My name is Akpos from Nigeria. I have finished manual testing course. Please, can someone advise me where to go on from here?

983

---

Login screen with Username, Password input fields,remember me check box,sign in and reset button write Test Cases for GUI, Funcitonal, Negative, Usability and Security testing.

2792

---

Write test cases on duster

4912

---

How many types of api testing are there?

1093

---