1) First check if all the tabs, menus and links are displaying proper pages
2) Put negative numbers into text fields
3) Put ridiculously long strings anywhere you can,
4) Paste inappropriate stuff - like binary files into text boxes
5) Open 13 instances of your app at once
6) Unplug the network or the power in the middle of an important flow
7) Change the system date and time
8) Install on a system way below the minimum specs
9) Use weird characters like ì È Ö
10) Run 10 other apps while you are testing
11) Delete crucial files
12) Don't close other applications before proceeding
13) Press submit button in all the forms for more than one time and see
the application response
14) Try to login with case sensitive passwords
15) Close your Browser while doing any uploading or submitting in the application
16) Test with low bandwidth networks
17) Change the parameter id’s displayed in the URL
18) View for Application icon in browser address bar
19) Check with the displayed error messages through out the application
20) Check whether the user can find on which page he is now (i-e) Application
have to highlight the current page
All looks like negative testing scenario's. Anyways all are good but not applicable to all applications.
ReplyDeleteThis isn't 'Habits of Highly Effective Testers' it's Testers 101. If you call yourself a software tester and don't know and do these tests, you have no business being a tester. I was anticipating an informative piece describing new or different things to try.
ReplyDeleteI disagree
ReplyDeleteA tester should always test in the scope of testing
Not performing negative testing does not mean that testing is not being performed
The project manageement team always has the decision that the testing team would not perform negative testing.
We should always first verify that the application works. Once we have determined that the application works then we should perform negative testing.
Moreover these are guidelines on how to design test cases - not habits
Instead of "Habits of Highly Effective Testers" u can change it to "Habits of Highly Effective Negative Testers" , this is more suitable and for negative testing above ways perfect.
ReplyDeleteNegative testing is required for any of the application but instead of verifying whether ur application is working fine in postive ceses or not, there is no importance of doing negative testing.
ReplyDeleteFirst do the positive testing and if all ceses are getting pass then start negative testing.
I don't agree with this. I would change the title to: "Habits of highly effective tests".
ReplyDeleteFor me these are clear examples of negative testing. Some examples are not, for example Open 13 instances of your app at once. That is not good, i agree that it is a negative attitude. But most of the listed items are example of negative tests, not negative testers. And negative testing must be conducted in any way at some point of the testing activity.
I think it's very useful list of "not to forget" items for testing.
ReplyDeleteI not agree with Anonymous said that we should first perform positive testing to verify (read to prove) that application works and then if we have time - perform negative testing.
In this case there are two serious mistakes:
1. It's simply incorrect testing approach.In this case we will never have time for negative testing.
2. It's not testers state of mind:) Tester should think about how to break application, should try do all possible actions that users could do. And users always input incorrect data in the fields.
To summarize, I want to say that you simply can't say that application works if you didn't perform negative testing. And if you will leave this to "if we have time" - it will never be done.
So, do positive and negative testing together!
first postitive testing (check the application works correctly) after that negative testing (if u have time)
ReplyDeleteReally worth list...
ReplyDelete