Interested to Buy Any Domain ? << Click Here >> for more details...
How will you review test cases?
- 26 Answers
- 55867 Views
- HCL, TCS, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
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.
| Is This Answer Correct ? | 1 Yes | 1 No |
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 .
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / geetha
plz mail me the requirement tracibility matrix for me
also...
Mail ID:geethalakshmic@gmail.com
thanks in advance
| Is This Answer Correct ? | 0 Yes | 0 No |
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.
| Is This Answer Correct ? | 0 Yes | 0 No |
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.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / akanksha goel
Please mail the Requirement Tracibility Matrix templete to
me
akankshaa410@gmail.com
| Is This Answer Correct ? | 0 Yes | 0 No |
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
| Is This Answer Correct ? | 2 Yes | 3 No |
Answer / srinivasreddy.b
what is exact answer i am so much confusion.
| Is This Answer Correct ? | 0 Yes | 1 No |
Hi.........can any one tell me the basic format for writing test cases
can anyone send me a copy of a business requirement and test cases attributed to such requirent. thank u
Given the following code, which is true about the minimum number of test cases required for full statement and branch coverage: Read P Read Q IF P+Q > 100 THEN Print “Large” ENDIF If P > 50 THEN Print “P Large” ENDIF how to find statement and branch coverage? Explain in brief?
There is project earlier it was developed in VB then they had replaced the project by java and there is no documentation available then how you are going to check that project. (Hint: - Parallel Testing).
Suppose an Application has been maintain from 4 years, we have written 5000 test cases for that. Now the functional flow has been changed for a Page. If I want to write test cases for that newly built page. How can I find what was there in that page 4 years back? How can we traced out? What is the best way to find test cases other than tracability?
How to write a test cases for the following Please it is urgent Once user clicks that link Invite Friend page opens up thru which user can do 2 functions - first is to search friends detail(name, mail id) from her address book in other sites (india times, yahoo, gmail and rediff) and second to mail the invite to the selected person/s. User can send invite to multiple person at same time. Searching friends detail in other address books will work like this: - User will input name, email id, pwd etc, select from which site she want to get friends list and then click on Import. - Users address book from other sites will be imported in one shot(first time) to iDiva database. - It will be arranged in alphabetical order(complete list) and mail ids which are already used will be in different color. - User will be able to update her address book by clicking on ""Refresh"" button on the page, which will trigger the process again, and fetch new mail ids.
What we do when the Requirements are continuously changed?
when you don't have time to write test cases, what do you do?
write a test case for a pen and paper regarding writing.
(questions asked in interview)hi every one can any one please answer to this questions.these questions were asked in an interview.i have another interview next week . 1.when the time schedule is tight how will you approch the testing,and the relese is nearing and we need to finish testing how can we follow in that case.do we need to exicute all the test cases or can priortise and leave some to next relase. 2. when a new feature is added to the existing application we need to add new test cases but after that do we need to change all the existing test cases and while running do we need to exicute entire application test cases or only the new feature test cases and related new feature test cases. 3.do you have any situation where you have to write and exicute the test cases same time, how will you follow.does it happens in real time. 4.example of bug which is not reproducible.like tester say that there is bug and developer say no can some example of such bugs. 5.during regression testing some times do we need to add new some additional test cases to test that bug.
test cases for landline phone
How to write simple test cases?
Automation Testing 
