Unit testing
Removed "Agile" section because a) it cited no sources, b) Agile is not prescriptive in that way, c) it conflated Scrum ("sprints") with Agile, d) it incorrectly dictated when actions should occur in sprints.
| ← Previous revision | Revision as of 13:34, 23 April 2026 | ||
| Line 86: | Line 86: | ||
|url-status=dead |
|url-status=dead |
||
}} |
}} |
||
== Agile == |
|||
{{Main|Agile software development}} |
|||
Sometimes, in Agile software development, unit testing is done per [[user story]] and comes in the later half of the sprint after requirements gathering and development are complete. Typically, the developers or other members from the development team, such as [[Information technology consulting|consultants]], will write step-by-step 'test scripts' for the developers to execute in the tool. Test scripts are generally written to prove the effective and technical operation of specific developed features in the tool, as opposed to full fledged business processes that would be interfaced by the [[end user]], which is typically done during [[user acceptance test]]ing. If the test-script can be fully executed from start to finish without incident, the unit test is considered to have "passed", otherwise errors are noted and the user story is moved back to development in an 'in-progress' state. User stories that successfully pass unit tests are moved on to the final steps of the sprint - Code review, peer review, and then lastly a 'show-back' session demonstrating the developed tool to stakeholders. |
|||
== Test-driven development == |
== Test-driven development == |
||
