<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://debianws.lexgopc.com/wiki143/index.php?action=history&amp;feed=atom&amp;title=Dynamic_testing</id>
	<title>Dynamic testing - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://debianws.lexgopc.com/wiki143/index.php?action=history&amp;feed=atom&amp;title=Dynamic_testing"/>
	<link rel="alternate" type="text/html" href="http://debianws.lexgopc.com/wiki143/index.php?title=Dynamic_testing&amp;action=history"/>
	<updated>2026-05-04T20:58:09Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.1</generator>
	<entry>
		<id>http://debianws.lexgopc.com/wiki143/index.php?title=Dynamic_testing&amp;diff=3217980&amp;oldid=prev</id>
		<title>81.104.196.152: Insert copula</title>
		<link rel="alternate" type="text/html" href="http://debianws.lexgopc.com/wiki143/index.php?title=Dynamic_testing&amp;diff=3217980&amp;oldid=prev"/>
		<updated>2025-06-02T14:16:28Z</updated>

		<summary type="html">&lt;p&gt;Insert copula&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{Refimprove|date=February 2023}}&lt;br /&gt;
&lt;br /&gt;
In [[software development]], &amp;#039;&amp;#039;&amp;#039;dynamic testing&amp;#039;&amp;#039;&amp;#039; (or &amp;#039;&amp;#039;&amp;#039;dynamic analysis&amp;#039;&amp;#039;&amp;#039;) is examining the [[Runtime (program lifecycle phase)|runtime]] response from a software system to particular input ([[test case]]). &lt;br /&gt;
&lt;br /&gt;
Tests can be run manually or via [[test automation|automation]]. &lt;br /&gt;
&lt;br /&gt;
[[Unit testing]], [[integration testing]], [[System testing]] and [[acceptance testing]] are forms of dynamic testing.&lt;br /&gt;
&lt;br /&gt;
In contrast to [[static testing]], the software must be runnable. &lt;br /&gt;
&lt;br /&gt;
== Evaluation ==&lt;br /&gt;
Advocates for dynamic testing cite that it can help identify weak areas in a [[runtime environment]], supports application analysis even when the tester cannot access the source code, it can identify vulnerabilities that are difficult to find via static testing, and that it can verify the correctness of [[static testing]] results.&lt;br /&gt;
&lt;br /&gt;
However, critics of dynamic testing cite that automated testing tools may give the wrong security, automated testing tools can generate false positives and negatives, and that dynamic testing makes it more expensive to fix bugs, as tracking them down can be more difficult, taking longer than needed.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
* [[Dynamic load testing]]&lt;br /&gt;
* [[Dynamic program analysis]]&lt;br /&gt;
* [[Time Partition Testing|Time partition testing]], a model-based testing methodology for the reactive test of dynamical or control systems.&lt;br /&gt;
* [[Daikon (system)|Daikon]], a dynamic invariant generator.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* G.J. Myers, &amp;#039;&amp;#039;The Art of Software Testing&amp;#039;&amp;#039;, [[Wiley (publisher)|John Wiley and Sons]], New York, New York, 1979.&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
&lt;br /&gt;
* [http://portal.acm.org/citation.cfm?id=370049.370462 Dynamic software testing of MPI applications with umpire]&lt;br /&gt;
&lt;br /&gt;
[[Category:Software testing]]&lt;br /&gt;
[[Category:Software development]]&lt;br /&gt;
[[Category:Software development process]]&lt;/div&gt;</summary>
		<author><name>81.104.196.152</name></author>
	</entry>
</feed>