Acceptance test-driven development: Difference between revisions

Content deleted Content added
Woden (talk | contribs)
m Woden moved page Acceptance test–driven development to Acceptance test-driven development over redirect: https://en.wikipedia.org/wiki/Hyphen "The hyphen (not the dash) is a punctuation mark used to join words"
No edit summary
Line 16:
=== Testing strategy ===
 
Acceptance tests are a part of an overall testing strategy. They are the customer/user oriented tests that demonstrate the business intent of a system. ComponentDepending testson areyour technicaltest acceptancestrategy, testsyou developedmay byuse anthem architectin thatcombination specifywith theother behaviortest oftypes, large modulese.g. lower level 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 includesincluding 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 ==