| Article Index |
|---|
| Testing Portal functionality without using automated tools |
| Page 2 |
| Page 3 |
| All Pages |
History. Review defects found and look for similar issues on subsequent releases. People often make similar mistakes and bugs found in one area will likely appear in other areas. Shift testing to cover conditions you suspect based on your experience with the product and the developers. Once some areas of code have "tightened up," shift your test ideas again. This is one reason exploratory testing works so well. Product changes and bugs move with the product. Here's an example based on experience -- credit card processing of expired cards. Once multiple bugs were found in this area and so this area remained high on the priority list for multiple releases. Once the issues had been cleared, still a test or two has to be executed because it was a high risk area but downshift how much time you spent on this area and move onto something else. Historical product knowledge can be a great help in planning testing.
Issue tracking. As your website continues to roll out releases into production, keep a healthy list of what you're not accomplishing -- which is often what we don't enjoy talking about. But it is best to discuss where you feel risks may not be addressed. Share this list with your stakeholders so that they're not lulled into thinking you've got it all figured out. Also keep in touch with customer support to know what issues have been found in production. You might alter your testing based on this feedback. You might be able to identify to your stakeholders the areas that could be covered with more time, staff or a tool.
This issue list will be your list to help grow your team and advocate for potential automated tool purchases. It isn't an excuse list or a list to hide behind, it's a reality list. You will never meet a product that was tested for every condition that you could think of, but you can find many products and websites that worked well under production use. What doesn't get tested is a potential business risk and those risks should be discussed in ongoing dialogs.
Subscribe to this comment's feed
| < Prev | Next > |
|---|
