Scribd
Upload
43 views2 pages

Classic Tester Errors

Some classic testing mistakes include focusing too much on functional testing and not enough on other types like configuration, stress, and load testing. Testing efforts also commonly start too late, fail to identify risky areas, and do not involve domain experts or seek diversity in testing teams. Specific mistakes that individual testers make include paying more attention to running tests than designing them, having test suites only they can understand, and not testing areas outside the visible interface.

Uploaded by

Alexandru Grigorescu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
43 views2 pages

Classic Tester Errors

Some classic testing mistakes include focusing too much on functional testing and not enough on other types like configuration, stress, and load testing. Testing efforts also commonly start too late, fail to identify risky areas, and do not involve domain experts or seek diversity in testing teams. Specific mistakes that individual testers make include paying more attention to running tests than designing them, having test suites only they can understand, and not testing areas outside the visible interface.

Uploaded by

Alexandru Grigorescu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Some Classic Testing Mistakes

The role of testing

 Thinking the testing team is responsible for assuring quality.


 Thinking that the purpose of testing is to find bugs.
 Not finding the important bugs.
 Not reporting usability problems.
 No focus on an estimate of quality (and on the quality of that estimate).
 Reporting bug data without putting it into context.
 Starting testing too late (bug detection, not bug reduction)

Planning the complete testing effort

 A testing effort biased toward functional testing.


 Underemphasizing configuration testing.
 Putting stress and load testing off to the last minute.
 Not testing the documentation
 Not testing installation procedures.
 An overreliance on beta testing.
 Finishing one testing task before moving on to the next.
 Failing to correctly identify risky areas.
 Sticking stubbornly to the test plan.

Personnel issues

 Using testing as a transitional job for new programmers.


 Recruiting testers from the ranks of failed programmers.
 Testers are not domain experts.
 Not seeking candidates from the customer service staff or technical writing staff.
 Insisting that testers be able to program.
 A testing team that lacks diversity.
 A physical separation between developers and testers.
 Believing that programmers can't test their own code.
 Programmers are neither trained nor motivated to test.

The tester at work

 Paying more attention to running tests than to designing them.


 Unreviewed test designs.
 Being too specific about test inputs and procedures.
 Not noticing and exploring "irrelevant" oddities.
 Checking that the product does what it's supposed to do, but not that it doesn't do what it isn't
supposed to do.
 Test suites that are understandable only by their owners.
 Testing only through the user-visible interface.
 Poor bug reporting.
 Adding only regression tests when bugs are found.
 Failing to take notes for the next testing effort.

Test automation

1
 Attempting to automate all tests.
 Expecting to rerun manual tests.
 Using GUI capture/replay tools to reduce test creation cost.
 Expecting regression tests to find a high proportion of new bugs.

Code coverage

 Embracing code coverage with the devotion that only simple numbers can inspire.
 Removing tests from a regression test suite just because they don't add coverage.
 Using coverage as a performance goal for testers.
 Abandoning coverage entirely.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy