Battling software bugs

There are two ways to test software. One is to set your sights on the target and attack. Another is to move along and attack bugs as you come across them.

1. Before testing begins, the testing person should understand what is to be tested (might be the functional flow), how it should be tested (the way of inputs), and where it could be completed (result). To fix the target, you write test cases, applicable validation and the expected results, and then you start testing.

2. However the test cases have been made, you cannot move along the way at all. Some bugs might stand outside your direct path that can create issues later. Although the target is fixed, testing personal should take care of the other bugs that they find during testing, such as software standardization, logical mistakes, validation failure and runtime errors. They should take notes about the test cases that say where and how they identified the bugs.

Testing is like a battlefield. Although the target is fixed, the soldiers should always be alert about their intermediate attacks.

Rate this Tip To rate tips, you must be a member of SearchSoftwareQuality.com. Register now to start rating these tips. Log in if you are already a member. Digg This!     StumbleUpon     Del.icio.us    RELATED CONTENT Software testing models and approaches (Context-driven, Factory, Analytic, Quality, IV&V) Put a stop to software espionage by watermarking source code Testing databases, how online testing communities can ramp up skill sets Software Testing: New software testing technologies bring new challenges Software Testing Ezines Recognizing appropriate scenarios for context testing Rich Internet applications security testing checklist Seven steps for a quality change and configuration management program How to create performance testing workload models How to apply modeling techniques to support software testing Transitioning from AJAX to .NET what changes to expect in RIA's Software Testing Free tools for Agile testers Recording and running software load tests with JMeter Free Web proxy security tools software testers should get to know Best practices for Scrum and when to apply them How to deal with iteration issues in Agile Five steps to fostering better software tester and QA results How to stop developer vs. tester, quality-killing blame game Easing software performance testing and usability modeling pressures How to apply modeling techniques to support software testing Calculating mean time to failure in performance testing RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary black box  (SearchSoftwareQuality.com) context-driven testing  (SearchSoftwareQuality.com) load testing  (SearchSoftwareQuality.com) RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.