Testing: A Streamlined Approach

Member Submitted

characters to be displayed, scenario when the number of characters would exceed the size of the text box for the latter while preparing the ambiguity one needs to know the three possible solutions for the same.

  1. Number of characters would not exceed the size of the text box
  2. Horizontal Scroll bar
  3. Vertical Scroll bar

If the answer were to be either choice 2 or 3, then the immediate question would be on the final cursor position upon striking the return key, whether this would be on the starting or the final character. Ambiguities with foresight serves two purpose, identifying bugs at an earlier stage and saves time to get issues clarified specifically when the location of the business, development and testing team work from different time zones. Translating business requirements into test cases and mapping each test case to the requirement accords significance. On a generic note, the system is prone to be unstable when negative tests are performed. Hence clearly identifying the positive and negative logic and mapping both the types to the corresponding requirements and in turn to the actual field in the application is a good practice. One key differentiating factor would be preparing different set of test data for manual testing as well. A stitch in time saves nine!

Unpredictable is what would describe most systems generally! Many a times, we come across situations where a scenario would pass one day and fail the other, while the tester being in the dark. As we own responsibility for the outcome, it is our duty to substantiate the claims as well. One of the easiest ways to prove the validity is snapshots! An Alt+Print Screen on a simple word doc would suffice! Voila! No more tensions of any proof!

Checklists! The guiding star to keep us updated of the events. Checklists contribute to the quality of a software system by (1) bringing the experience of many people to bear on each situation and (2) standardizing the review process so that the results are independent of the participants. These lists include those items that we want to be certain are included in the system as well as those items that are most likely to contain defects.

Stop Knowing when to stop is a skill. Having identified the completion criteria in our initial stages metrics is all that helps us in determining the release threshold. A diligently maintained metrics is a living proof to project where we stand and what difference we have made as a tester in short, a true source for retrospection.

Happy Testing!!

About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.