Software testing controversies

Short description: Controversies about what constitutes responsible software testing

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)

This article contains weasel words: vague phrasing that often accompanies biased or unverifiable information. Such statements should be clarified or removed. (March 2009)

|

(Learn how and when to remove this template message)

There is considerable variety among software testing writers and consultants about what constitutes responsible software testing. Proponents of a context-driven approach[1] consider much of the writing about software testing to be doctrine, while others believe this contradicts the IEEE 829 documentation standard.[2]

## Contents

* 1 Best practices
* 2 Types of software testing
* 2.1 Agile vs. traditional
* 2.2 Exploratory vs. scripted
* 2.3 Manual vs. automated
* 2.4 Software design vs. software implementation
* 3 Oversight
* 4 References

## Best practices

Proponents of the context-driven approach believe that there are no best practices of testing, but rather that testing is a set of skills that allow the tester to select or invent testing practices to suit each unique situation. James Marcus Bach wrote "...there is no practice that is better than all other possible practices, regardless of the context."[3] However, some testing practitioners do not see an issue with the concept of "best practices" and do not believe that term implies that a practice is universally applicable.[4]

## Types of software testing

### Agile vs. traditional

Around 1990, a new style of writing about testing began to challenge previous approaches. The seminal work in this area is often regarded as Testing Computer Software by Cem Kaner.[5] Instead of the assumption that testers have full access to source code and complete specifications, these writers, including Kaner and James Bach, argued that testers must learn to work under conditions of uncertainty and constant change. Meanwhile, an opposing trend toward process "maturity" also gained ground, in the form of the Capability Maturity Model. The agile testing movement, which includes but is not limited to testing methods practiced on agile development projects, is popular mainly in commercial circles, whereas CMM was embraced by government and military software providers.

However, saying that "maturity models" like CMM gained ground against or opposing Agile testing may not be right. Agile movement is a 'way of working', while CMM is a process improvement idea.

But another point of view must be considered: the operational culture of an organization. While it may be true that testers must have an ability to work in a world of uncertainty, it is also true that their flexibility must have direction. In many cases test cultures are self-directed and as a result fruitless, unproductive results can ensue. Furthermore, providing positive evidence of defects may either indicate that you have found the tip of a much larger problem, or that you have exhausted all possibilities. A framework is a test of Testing. It provides a boundary that can measure (validate) the capacity of our work. Both sides have continued to debate the merits of their approaches, but the true measure lies in assessing delivery quality. Testing systematically without broader focus can be ineffective, while finding numerous errors does not necessarily mean Agile methods were the cause; it may simply indicate poor initial work.

### Exploratory vs. scripted

Exploratory testing means simultaneous test design and test execution with an emphasis on learning. Scripted testing means that learning and test design happen prior to test execution, and quite often the learning has to be done again during test execution.[6] Exploratory testing is very common, but in most writing and training about testing it is barely mentioned and generally misunderstood. Some writers consider it a primary and essential practice. Structured exploratory testing is a compromise when the testers are familiar with the software. A vague test plan, known as a test charter, is written up, describing what functionalities need to be tested but not how, allowing the individual testers to choose the method and steps of testing.

There are two main disadvantages associated with a primarily exploratory testing approach. The first is that there is no opportunity to prevent defects, which can happen when the designing of tests in advance serves as a form of structured static testing that often reveals problems in system requirements and design. The second is that, even with test charters, demonstrating test coverage and achieving repeatability of tests using a purely exploratory testing approach is difficult. For this reason, a blended approach of scripted and exploratory testing is often used to reap the benefits while mitigating each approach's disadvantages.

### Manual vs. automated

Some writers believe that test automation is so expensive relative to its value that it should be used sparingly.[7] Others, such as advocates of agile development, recommend automating 100% of all tests. A challenge with automation is that automated testing requires automated test oracles (an oracle is a mechanism or principle by which a problem in the software can be recognized). Such tools have value in load testing software (by signing on to an application with hundreds or thousands of instances simultaneously), or in checking for intermittent errors in software.

The success of automated software testing depends on complete and comprehensive test planning. Software development strategies such as test-driven development are highly compatible with the idea of devoting a large part of an organization's testing resources to automated testing. Many large software organizations perform automated testing. Some have developed their own automated testing environments specifically for internal development, and not for resale.

### Software design vs. software implementation

[non sequitur]

if software testing is gathering information on a product or program for stakeholders then it doesn't follow that there is a choice between testing implementation or design - i.e. this is a faulty assumption.[clarification needed] Ideally, software testers should not be limited only to testing software implementation, but also to testing software design. With this assumption, the role and involvement of testers will change dramatically. In such an environment, the test cycle will change too. To test software design, testers would review requirement and design specifications together with designer and programmer, potentially helping to identify bugs earlier in software development.[8]

## Oversight

One principle in software testing is summed up by the classical Latin question posed by Juvenal: Quis Custodiet Ipsos Custodes (Who watches the watchmen?), or is alternatively referred informally, as the "Heisenbug" concept (a common misconception that confuses Heisenberg's uncertainty principle with observer effect). The idea is that any form of observation is also an interaction, that the act of testing can also affect that which is being tested.[9]

In practical terms, the test engineer is testing software (and sometimes hardware or firmware) with other software (and hardware and firmware). The process can fail in ways that are not the result of defects in the target but rather result from defects in (or indeed intended features of) the testing tool.

There are metrics being developed to measure the effectiveness of testing. One method is by analyzing code coverage (this is highly controversial) - where everyone can agree what areas are not being covered at all and try to improve coverage in these areas.

Bugs can also be placed into code on purpose, and the number of bugs that have not been found can be predicted based on the percentage of intentionally placed bugs that were found. The problem is that it assumes that the intentional bugs are the same type of bug as the unintentional ones.

Finally, there is the analysis of historical find-rates. By measuring how many bugs are found and comparing them to predicted numbers (based on past experience with similar projects), certain assumptions regarding the effectiveness of testing can be made. While not an absolute measurement of quality, if a project is halfway complete and there have been no defects found, then changes may be needed to the procedures being employed by QA.

## References

1. ↑ "Principles" (in en-US). https://context-driven-testing.com/.
2. ↑ Bath, Graham; Veenendaal, Erik Van (2013-12-13) (in en). Improving the Test Process: Implementing Improvement and Change - A Study Guide for the ISTQB Expert Level Module. Rocky Nook, Inc.. ISBN 978-1-4920-0133-1. https://books.google.com/books?id=oT-4BAAAQBAJ&dq=IEEE+829+test+documentation+standard&pg=PT51.
3. ↑ Bach, James (8 July 2005). "No Best Practices". http://www.satisfice.com/blog/archives/27.
4. ↑ Colantonio, Joe (13 April 2017). "Best Practices Vs Good Practices – Ranting with Rex Black". https://www.joecolantonio.com/2017/04/13/best-practices-rant/.
5. ↑ Kaner, Cem; Jack Falk; Hung Quoc Nguyen (1993). Testing Computer Software (Third ed.). John Wiley and Sons. ISBN 1-85032-908-7.
6. ↑ Atlassian. "Exploratory Testing" (in en). https://www.atlassian.com/continuous-delivery/software-testing/exploratory-testing.
7. ↑ An example is Mark Fewster, Dorothy Graham: Software Test Automation. Addison Wesley, 1999, ISBN 0-201-33140-3
8. ↑ "Shifting the Balance of Cybersecurity Risk: Principles and Approaches for Security-by-Design and -Default" (in en-US). 2023-04-13. https://www.cisa.gov/sites/default/files/2023-04/principles_approaches_for_security-by-design-default_508_0.pdf.
9. ↑ Garcia, Boni (2017-10-27) (in en). Mastering Software Testing with JUnit 5: Comprehensive guide to develop high quality Java applications. Packt Publishing Ltd. ISBN 978-1-78712-439-4. https://books.google.com/books?id=xxhKDwAAQBAJ&dq=Software+testing+who+watches+the+watchmen&pg=PA286.

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Software testing controversies. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software_testing_controversies&oldid=3977477"