Interested to Buy Any Domain ? << Click Here >> for more details...
How will you review test cases?
- 26 Answers
- 55872 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 |
Write the 10 test cases for Telephone/Pen.
Write all Possible (+ve and -ve) Test Cases for a Date Object (DD/MM/YYYY) which is entered manually?
What are the test scenario's for pen like high priority high seviority?
4 Answers NetWeb, Zycus Infotech,
How many test cases you will execute per day?
hi iam working in HCL as a fresher n iam dg automation testing i am going to give client demo i did some 7 scripts i want to call all those in some new page in QTP I KNOW CALL THE EXISTING ACTION N COPY OF ACTION if we use any of these options while running it will show the whole script but is there any other method while running it should not show the whole script it will show only the calling lines plz give me detailed explanation to ds i need reply fast plzz
test cases for landline phone
In a log in page what will be test procedure, test scenario, test description & test steps?
Requirement from Market “Alice is talking to Bob. Bob thinks that Alice should talk to Chris for more information. Currently, Bob will pass on the directory number of Chris to Alice; Alice/Bob will disconnect the call and then Alice will initiate a new call to Chris. What we need need, Bob should be able to transfer the call to Chris, without Alice making another call.” Implementation done by Unified CM Development Team When a basic call is connected, a new softkey “Transfer” will be displayed on the IP Phone. User (say, Bob) can press that and dial a target (say, Chris). Bob has two options (1) wait for Chris to answer and then tell Chris about call from Alice and then press “transfer” again to complete transfer (2) press “Transfer” immediately; when Chris answers he will be connected to Alice Please come up with test cases thinking from a user perspective, let’s say from a Bank (there could be users such as receptionists, accountants, managers etc.) – in what all scenarios transfer can happen, any negative scenarios (cases where we don’t get a positive response always). If you think you need an enhancement to the feature, please go ahead and suggest that as well.
If I have written the 10 Positive test cases first and Negative test cases 11 to 25 .I Execute +ve first & then - ve as per test cases were written .Now if I got the next build & if I write again +ve Test Cases 26-30 first & then - ve 31-35 but I have to execute all test cases 1 to 35.But here the sequence of execution is +ve,-ve,+ve & -ve .How should I maintain the test cases .Please tell me It's Urgent .Thanks In Advance.....Tester
Hai, Could anybody please let me know, how to calculate the number of test cases required to test a program. Please provide me the answer for the following question: “What type of ticket do you require, single or return?”IF the customer wants ‘return’Ask: “What rate, Standard or Cheap-day?”IF the customer replies ‘Cheap-day’Say: “That will be $11:20”ELSESay: “That will be $19:50”ENDIFELSESay: “That will be $9:75”ENDIFNow decide the minimum number of tests that are needed to ensure that allthe questions have been asked, all combinations have occurred and allreplies given. a) 3 b) 4 c) 5 d) 6
How about do we go as far as writing test cases is considered?
Explain the scalability testing?
Automation Testing 
