Content deleted Content added
Reverted to revision 940544426 by GreenC bot (talk): MOS:LQ - if the punctuation is not in the original, we do not include it. (TW) |
m MOS:PUNCT and formatting |
||
Line 16:
=== Testing strategy ===
Acceptance tests are a part of an overall testing strategy. They are the customer tests that demonstrate the business intent of a system. Component tests are technical acceptance tests developed by an architect that specify the behavior of large modules. Unit tests are created by the developer to drive easy-to-maintain code.<ref>[Test-driven_development]</ref> They are often derived from acceptance tests and unit tests. Cross-functional testing includes usability testing,<ref>Meszaros, Gerard, and Janice Aston. (2006) "Adding Usability Testing to an Agile Project." Agile Conference</ref> exploratory testing,<ref>{{cite web | title = Exploratory Testing Explained | url = http://www.satisfice.com/articles/et-article.pdf }}</ref> and property testing (scaling and security).<ref>Meszaros, Gerard.(2007) ''xUnit Test Patterns: Refactoring Test Code''. Addison-Wesley.</ref>
== Acceptance criteria and tests ==
Acceptance criteria are a description of what would be checked by a test. Given a requirement such as
=== Test format ===
| |||