Answer / senz

Review of TC is checking the written TCs by a colleague or
test lead in order to know that those are correct or any
misunderstandings in the requirements or anything missed
out.

Answer / sharad chaudhary

after creating test case when review will strat we are
simple checking all client requirment are fullfil and
these requirment are mation for right set of action .

Answer / shiva

Please mail the Requirement Tracibility Matrix templete to
me
also my mail id : shiva.shanker27@rediffmail.com

Answer / geetha

plz mail me the requirement tracibility matrix for me
also...

Mail ID:geethalakshmic@gmail.com

thanks in advance

Answer / sandeep

Utility Value: The first thing to review in a test case is its utility value. Is this test case required? Is this testing something which has already been covered in some other test case? Is this testing something too little? There has to be definite value which this test case provides. And it should test a requirement or feature which is mentioned in the specifications of the system.
Test Case Objective: When you go through the test case for review, check if you are able to understand the objective of the test case. A good test case should have a single objective. In case there are multiple objectives that are being tested, then you should recommend that the complex test case be broken down into more simple test cases.
Pre-Requisites: Does the test case require any special setup to be done before execution? Is there any action to be taken before-hand? Has this been mentioned clearly in the test case?
Steps: Does the test case contain step wise instructions to be followed for executing the test case? Can a new tester attain the objective by following the test steps? If not, then the test case writer is presuming some steps, and has missed to put in the necessary steps in the test case.
Inputs: The test case should clearly specify what values to be given as inputs in the test case. Nowhere should it have instructions mentioning, enter any number, or string, as that may cause the test case to return different results every time.
Language: The language used in the test case should be simple and unambiguous. There should be no scope for interpreting the test case in any other manner except the desired one.
Results: A good test case should clearly mention what is the expected result and behaviour of the system. Determination of whether the test passes or fails should be fairly straight forward.
Clean-up: If the test case has changed the state of the system in such a way that subsequent test cases may get affected, then it should have steps which undo these changes to ensure there is no impact on the subsequently executing tests.
Dependencies: Does this test case have any dependencies with any other test cases? Are they to be executed before or after this test case? If yes, this too needs to be clearly documented in the test case. Ideally every test case should have its own individuality with no dependencies on others. Where it cannot be avoided, then it should be documented very clearly.
Documentation: A test case should clearly mention the name of the author, the test case priority (if applicable), and the specific requirement which it tests so as to help in doing traceability to find out the test coverage.

Answer / raghavendra kc

Test case review requires following check points:

1.whether test cases covered all the use case scenarios mentioned in requirement document. This can be verified by using Requirement Tracability Matrix or can prepare own xl sheet to track use case coverage
2. Whether Test Case objecive meets the functionality properly and understandable by others
3. Test Steps includes Pre condition, test steps, expected results maps the use case/requirement specification and are understandable.

Answer / vidya

I am agree with Kishore Kumar.
Kishore u r rite.

Answer / akanksha goel

Please mail the Requirement Tracibility Matrix templete to
me


akankshaa410@gmail.com

Answer / amit

Hi guys,

i read above all the answers, can anyone of u plz mail me d
design with example,how does this Requirement Tracibility
Matrix looks like ? please mail me at: ontesting@gmail.com
Right now we just go through srs/frs to make test cases.
Please do this favor by mailing me this, in excel sheet.

Thnx so much,
Amit

Answer / srinivasreddy.b

what is exact answer i am so much confusion.

Explain the soak testing?

0 Answers  

What is Unit Testing ? What is Integration Testing ? What is acceptance testing ? What is Static testing? What is System testing? What is Load Testing? What is Smoke Testing? What is Soak Testing? What is Scalability Testing? What is Sanity Testing? What is Ramp Testing? What is Monkey Testing? What is Gray Box Testing? What is Functional Testing? What is Glass Box Testing? What is Dynamic Testing? What is Compatibility Testing? What is Concurrency Testing? What is Component Testing? What is Ad Hoc Testing? What is Agile Testing?

1 Answers  

if software faild in customer environment what we called a)error b)fault c)defect d)failure

5 Answers   ITC Infotech,

Please can any one tel how to write the test cases for these Requirements:- 1.The applications sends the periodic data 2.The applications sends the alarm data 3.The Application stores the Periodic data and alarm data if it is unable to send 4.the application having the configure through GPRS or SMS

0 Answers  

i'm confused to wite a Test Scenarios. can any one help me how to start?

3 Answers   IBM,

Elaborate test plan and content availability in test plan.

0 Answers  

What is ramp testing?

0 Answers  

what will be the test case for Lift?

22 Answers   Mind Tree, Satyam, Tops Security Ltd,

Is there any formula to find the number of test cases needed

4 Answers   Satyam,

Explain the domain testing?

0 Answers  

Test cases on uplaoding files

12 Answers   GE, HP,

can any one give the format of writing test cases in excel sheet.

33 Answers   Aricent,