Can test case contains more than 50 steps in single test
case?
Answers were Sorted based on User's Feedback
Answer / sameena
Hi,
That will show a poor tester.
U'r test case should be crisp and short.
Is This Answer Correct ? | 5 Yes | 0 No |
Answer / hema
it doesn't matter abt the no of test steps,its important
that the testcases should be understandable by the client.
all the steps should be necessary.unnecessary steps should
be avoided.
Is This Answer Correct ? | 2 Yes | 1 No |
Answer / hemaiyer
A good test engineer always provide a high quality
software for a single test cases 50 steps are written
provided their should not be repeated test steps in the
test cases
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / sathish
It can be more than 50 Steps, but the developer who fixes the bug will not be interested in reading all blah-blah stories. instead you can break the case into small modules ( functionality ,UI ,validation ..etc) or functionality itself into easy phases to make it easy readable form.
Is This Answer Correct ? | 0 Yes | 1 No |
Explain the monkey testing?
do we write separate test cases for each type of testing? for example for functional testing and integration testing,we write two seprate test case documents or just one?please explain.
I need GUI test case for home page?
if u want to test an application which takes a data value between 0 and 59 and if u choose 55 ,what type of testing it is a) System testing b) error guessing c) Black box d) None
write test case for white board marker.
suppose an interviewer asks you to write a testcase for a login window (and application is not given to test). Should we write actual results or expected results or both?
can you tell me how to write test cases for payments, receipts, inward clearing, outward clearing, A/c statements ?
Write test case for a search engine?
12 Answers Saba, Saba Software,
How to test Webservices and how can we write test cases for that
how do u knw when to stop writing test case for a given project.
Write test case for windows media player
IF A > B THEN C = A – B ELSE C = A + B ENDIF Read D IF C = D Then Print "Error" ENDIF A. 1 test for statement coverage, 3 for branch coverage B. 2 tests for statement coverage, 2 for branch coverage C. 2 tests for statement coverage. 3 for branch coverage D. 3 tests for statement coverage, 3 for branch coverage E. 3 tests for statement coverage, 2 for branch coverage