| || |
- 1 Post By dlai
How to write test case for Login form - where 15+ text box with different validation
1. Registration Program ID: (Mandatory)
3. Category: (list box, select from drop down)
4. Address Line 1:
5. Address Line 2
9. Zip code
10. Start Date
11. End Date
12.. Invite Date
13. Reminder Date
14. Tickets Available:
15. Contact Person
17. Selection Process:
18. EVENT TYPE
How to write Test Cases for this page having all above data feilds ?
You have to consider,
1) who is reading your test cases
if it's for outsourced, i may write in more details and more granular, if it's for someone in house an intelligence, I may be more high level and say, "validate form validations work for required fields" and not explain every nuance of how each error message looks like.
2) what is important in the feature
I'm sure there are some fields by virtue of how the product works or the business that's more important than others. For example, some of those fields you know has very little business logic, like a contact person most likely is just a simple pass through field. Where the program ID maybe is validated against another existing entity.
3) what is likely to break
At some point, test cases you write will become regression tests. You might want to start thinking, if I were running this over and over again, how can I cut things out? For example, a simple null field validation, do you really want to validate that with every build? You may find ways to simplify or just cut those tests out completely and move those to some sort of exploratory test plan.