I have to write test cases for Create User, Edit User,
Delete User etc.
Some of the steps for Create & Edit User are same.
Then Should I write refer Create User [test case Id] for
common test steps to write Edit User Test case?
OR I have to write separate test steps even though they are
repeatable in Create user & Edit User test case.
Answers were Sorted based on User's Feedback
Answer / sunshine
Hi,
I think it is good to have all the steps present in the same
test case instead of linking or pointing elsewhere because
of the reasons below
1:A test case should be self sufficient.Should have all the
details of execution in the test case itself.
2:What if the create user steps change in future and they
are not the same as edit user?
3:What if for some reason the tester of edit user does not
have access to create user cases?
4:When we link one to other we always have dependency and
when one changes we have to be cautious about the other.
5:Can create maintenance problems
So my suggestion is not to have links.
I also have a suggestion about testing if you do not mind.
There is one amazing site which can make your testing easy.
http://www.testersdesk.com/
There is one tool Person Name Generator which can generate
user names which can be quite useful for your automation and
manual testing. There are a whole bunch of other test data
generation,test case design and other useful tools available
for free at one place. Have a look!
| Is This Answer Correct ? | 10 Yes | 1 No |
Answer / rudraneel
Create a Template Test Case, which will contain similar
steps.Call that template where ever you feel necessary,
that means; if you feel that same steps you need to write
again, call there that template.
| Is This Answer Correct ? | 5 Yes | 6 No |
what is Application state,Base state and call state?
wat is test scenario
Difference b/n Validation and verification?
I Have 2 Yrs Experience in Manual I appiled in Job Portals still i m not getting any calls plz help me wat i need to do guide me please ?
How do you test if you have minimal or no documentation about the product?
1.Test cases for Password cannot be used for next 13 times? 2.Test cases for Password should not be less than 8 to 13 chars and there should be at least one special character and one Capital letter.
How can I do a documentation of Test Cases? Which steps are in it?
what is the output of the query select * from emp where 1=2
which type of questins we can expect for Banking domain
what does 80hz refresh rate indicates?
1.what is the purpose of testing ?
If a bug has high severity then usually that is treated as high priority,then why do priority given by test engineers/project managers and severity given by testers?