Dynamic testing

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Dynamic testing" – news · newspapers · books · scholar · JSTOR (February 2023) (Learn how and when to remove this message)

In software development, dynamic testing (or dynamic analysis) is examining the runtime response from a software system to particular input (test case).

Tests can be run manually or via automation.

Unit testing, integration testing, System testing and acceptance testing are forms of dynamic testing.

In contrast to static testing, the software must runnable.

This section is in list format but may read better as prose. You can help by converting this section, if appropriate. Editing help is available. (April 2019)

Proponents cite that dynamic testing:

• can identify weak areas in the runtime environment
• supports application analysis even when the tester cannot access the source code
• can identify vulnerabilities that are difficult to find via static testing
• can verify the correctness of static testing results

Critics cite that:

• Automated tools may give the wrong security, such as check everything
• Automated tools can generate false positives and negatives
• Dynamic testing is hard to track down the vulnerabilities in the code, and it takes longer to fix the problem, therefore, fixing bugs is expensive

• Dynamic load testing
• Dynamic program analysis
• Time partition testing, a model-based testing methodology for the reactive test of dynamical or control systems.
• Daikon, a dynamic invariant generator.

• G.J. Myers, The Art of Software Testing, John Wiley and Sons, New York, New York, 1979.

• Dynamic software testing of MPI applications with umpire