<?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=Orthogonal_array_testing</id>
	<title>Orthogonal array 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=Orthogonal_array_testing"/>
	<link rel="alternate" type="text/html" href="http://debianws.lexgopc.com/wiki143/index.php?title=Orthogonal_array_testing&amp;action=history"/>
	<updated>2026-04-30T20:50:36Z</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=Orthogonal_array_testing&amp;diff=3229534&amp;oldid=prev</id>
		<title>imported&gt;Citation bot: Removed parameters. | Use this bot. Report bugs. | Suggested by Headbomb | Category:CS1 maint: DOI inactive as of June 2024 | #UCB_Category 100/305</title>
		<link rel="alternate" type="text/html" href="http://debianws.lexgopc.com/wiki143/index.php?title=Orthogonal_array_testing&amp;diff=3229534&amp;oldid=prev"/>
		<updated>2024-06-12T22:16:15Z</updated>

		<summary type="html">&lt;p&gt;Removed parameters. | &lt;a href=&quot;/wiki143/index.php?title=En:WP:UCB&amp;amp;action=edit&amp;amp;redlink=1&quot; class=&quot;new&quot; title=&quot;En:WP:UCB (page does not exist)&quot;&gt;Use this bot&lt;/a&gt;. &lt;a href=&quot;/wiki143/index.php?title=En:WP:DBUG&amp;amp;action=edit&amp;amp;redlink=1&quot; class=&quot;new&quot; title=&quot;En:WP:DBUG (page does not exist)&quot;&gt;Report bugs&lt;/a&gt;. | Suggested by Headbomb | &lt;a href=&quot;/wiki143/index.php?title=Category:CS1_maint:_DOI_inactive_as_of_June_2024&amp;amp;action=edit&amp;amp;redlink=1&quot; class=&quot;new&quot; title=&quot;Category:CS1 maint: DOI inactive as of June 2024 (page does not exist)&quot;&gt;Category:CS1 maint: DOI inactive as of June 2024&lt;/a&gt; | #UCB_Category 100/305&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;Orthogonal array testing&amp;#039;&amp;#039;&amp;#039; is a systematic and [[Statistics|statistically-driven]] [[black-box testing]] technique employed in the field of [[software testing]].&amp;lt;ref&amp;gt;{{Cite book |last=Pressman |first=Roger S. |title=Software engineering: a practitioner&amp;#039;s approach |date=2005 |publisher=McGraw-Hill |isbn=978-0-07-285318-6 |edition=6th |series=McGraw-Hill series in computer science |location=Boston}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite book |last1=Phadke |first1=Madhav S. |last2=Phadke |first2=Kedar M. |title=2014 Reliability and Maintainability Symposium |chapter=Utilizing design of experiments to reduce IT system testing cost |date=January 2014 |chapter-url=http://dx.doi.org/10.1109/rams.2014.6798451 |pages=1–6 |publisher=IEEE |doi=10.1109/rams.2014.6798451|isbn=978-1-4799-2848-4 |s2cid=8081137 }}&amp;lt;/ref&amp;gt; This method is particularly valuable in scenarios where the number of inputs to a [[Software system|system]] is substantial enough to make exhaustive testing impractical.&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
Orthogonal array testing works on the premise of selecting a [[subset]] of test cases from a large [[Pool (computer science)|pool]] of potential inputs. This selection is based on statistical methods to ensure that the chosen subset represents the whole input space. As a result, serious [[Software bug|bugs]] can be identified while the number of tests necessary to do so is greatly reduced.&lt;br /&gt;
&lt;br /&gt;
=== Benefits ===&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Reduced testing cycle time&amp;#039;&amp;#039;&amp;#039;: By strategically selecting test cases, the testing process becomes more efficient, leading to time savings.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Simplified analysis&amp;#039;&amp;#039;&amp;#039;: The structured nature of orthogonal array testing makes analysis straightforward and less complex.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Balanced test cases&amp;#039;&amp;#039;&amp;#039;: This technique ensures that test cases are well-balanced, making it easier to isolate defects and assess performance.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Cost savings&amp;#039;&amp;#039;&amp;#039;: It offers a significant cost advantage over pair-wise testing, making it an economical choice for testing large-scale software systems.&lt;br /&gt;
&lt;br /&gt;
=== Cons ===&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Limited applicability&amp;#039;&amp;#039;&amp;#039;: This technique is most effective when the number of inputs is relatively small. In cases with an extremely large number of inputs, it may not be as efficient.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Complex implementation&amp;#039;&amp;#039;&amp;#039;: Properly designing orthogonal arrays requires a good understanding of statistical principles, which may pose a challenge for some testing teams.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;May miss specific edge cases&amp;#039;&amp;#039;&amp;#039;: While orthogonal arrays are designed to cover a broad range of scenarios, they may not capture very specific edge cases that could be crucial in certain applications.&lt;br /&gt;
&lt;br /&gt;
== Applications ==&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;[[User interface|User Interface]] Testing&amp;#039;&amp;#039;&amp;#039;: Orthogonal array testing is employed to evaluate the user interface of software applications. It aids in identifying interface-related anomalies and inconsistencies.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;[[System testing|System Testing]]&amp;#039;&amp;#039;&amp;#039;: It is used to validate the functionality of entire systems, ensuring that they perform as specified in their requirements.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;[[Regression testing|Regression Testing]]&amp;#039;&amp;#039;&amp;#039;: Orthogonal array testing is effective in the detection of regressions, ensuring that new updates or modifications do not introduce unintended consequences.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Configuration Testing&amp;#039;&amp;#039;&amp;#039;: This technique is valuable in assessing different configurations of software, ensuring compatibility across diverse environments.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;[[Software performance testing|Performance Testing]]&amp;#039;&amp;#039;&amp;#039;: It can be applied to evaluate the performance characteristics of software systems, helping to identify potential bottlenecks or performance issues.&lt;br /&gt;
&lt;br /&gt;
== Principle of Orthogonality ==&lt;br /&gt;
Orthogonal array testing works based on something called [[Orthogonal array|orthogonal arrays]].&amp;lt;ref&amp;gt;{{Cite web |date=2023-09-30 |title=What is Orthogonal Array Testing? (Example) |url=https://www.guru99.com/orthogonal-array-testing.html |access-date=2023-10-05 |website=www.guru99.com |language=en-US}}&amp;lt;/ref&amp;gt; These are organized lists of different factors. When we use them, we make sure that the results we get from each factor are not connected or related. This means each test gives us new and unique information. This way of organizing inputs helps us avoid repeating tests and get the same info with the least number of [[Experiment|experiments]].&lt;br /&gt;
&lt;br /&gt;
=== Orthogonal vector ===&lt;br /&gt;
The concept of orthogonal vectors in orthogonal arrays is fundamental to understanding orthogonal array testing. Orthogonal vectors possess key properties:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Unique Information&amp;#039;&amp;#039;&amp;#039;: Each vector imparts information distinct from any other vector in the sequence, thereby avoiding redundancy.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Separability&amp;#039;&amp;#039;&amp;#039;: Through linear addition, the signals can be easily separated.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Statistical Independence&amp;#039;&amp;#039;&amp;#039;: Each vector is statistically independent of the others, signifying a lack of correlation between them.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Resultant Summation&amp;#039;&amp;#039;&amp;#039;: When subjected to linear addition, the resultant is the arithmetic sum of the individual components&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* {{cite journal |last=Rao |first=Calyampudi Radhakrishna |year=2009 |title=Orthogonal arrays |journal=Scholarpedia |volume=4 |issue=7 |page=9076 |doi=10.4249/scholarpedia.9076|bibcode=2009SchpJ...4.9076R |doi-access=free }}&lt;br /&gt;
* {{cite web |url=http://www.york.ac.uk/depts/maths/tables/orthogonal.htm |first=Gustav W |last=Delius |title=Orthogonal Arrays (Taguchi Designs) |date=May 2004 |publisher=University of York}}&lt;br /&gt;
* {{cite web |url=http://support.sas.com/techsup/technote/ts723.html |title=Orthogonal Arrays |first=Warren F |last=Kuhfeld |publisher=SAS Institute Inc |quote=SAS provides a catalog of over 117,000 orthogonal arrays.}}&lt;br /&gt;
* {{cite web |url=https://paportal.phadkeassociates.net/learning.aspx |title=Planning Efficient Software Tests |first=Madhav S |last=Phadke |publisher=Phadke Associates, Inc. |quote=Numerous articles on utilizing Orthogonal Arrays for Software and System Testing. |access-date=2011-10-07 |archive-date=2012-04-25 |archive-url=https://web.archive.org/web/20120425051819/https://paportal.phadkeassociates.net/learning.aspx |url-status=dead }}&lt;br /&gt;
* {{cite web |url=http://phadkeassociates.com/index_rdexperttestplanning.htm |title=rdExpert Software for Orthogonal Array Testing |publisher=Phadke Associates, Inc. |archive-url=https://web.archive.org/web/20110114080303/http://phadkeassociates.com/index_rdexperttestplanning.htm |archive-date=2011-01-14 |quote=Commercial toolset for Orthogonal Array Testing.}}&lt;br /&gt;
&lt;br /&gt;
{{Software testing}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Survival analysis]]&lt;br /&gt;
[[Category:Design of experiments]]&lt;/div&gt;</summary>
		<author><name>imported&gt;Citation bot</name></author>
	</entry>
</feed>