Step 2. Try Testing
You are about to enter a two-page web site that is loaded with many common bugs.
Is this buggy site real?
The "Day Dream Travel" site is not a real site, but it is a good real-world example for two reasons:
1. The first delivery of code from the engineers is often very buggy. They've worked hard at just getting the features to work and getting everything hooked in. The pages may not be pretty yet and if many engineers worked on the project not all the features may work well with each other yet.
2. As testers, we don't always get a specification of how the web site is supposed to work or look. We must rely upon our knowledge and experience of how the web works. Sometimes we don't even have test cases to guide us in how or what to test.
How do I start?
1. Keep a pad of paper by your side to jot down (or open a word processing application in the background)
| · | the combinations of things that you try while you are testing. |
| · | the bugs that you find. |
2.Enter the Sample Buggy Web Site:
| · | Try to use the site the way you think a user would. |
| · | Try to do things that you don't think a user is likely to do but that might break the application. For example, what would happen if in an email address field the user entered training#vettanna.com? (# instead of @) Does the application give the user an error message, does it choke, or does it record exactly what the user wrote? |
| · | How do the pages look? Are they visually appealing? Is the content correct? |
| · | Try running the complete test case and the detailed test case described in the Day In The Life Of A Tester. |
3. That's enough clues to get you started. Rely on your instincts about what you think it should do. When you are sure that you've found all the bugs, click on 3. Enter a Bug Report to write up your bug reports.
What's a bug?
Anything that doesn't work (or look) the way you expected it to.
How do I know if my "expectation" is right?
For this sample, trust your instinct and believe that you are right. (In the Vettanna training class, we teach you how to find out what you should expect.)
How do I write up a bug report?
After you click on 3. Enter A Bug Report, you'll enter a bug database. This is a tool that testers spend a lot of time in. Do your best to enter and describe each of the bugs that you find. Don't stress, this isn't a test and nothing you do is wrong. This is just practice for you to try it out.
[an error occurred while processing this directive]