Timeline for Would a middle ground between unit and integration tests be optimal
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5, 2024 at 21:53 | comment | added | Thor | Thanks. I am looking for a good term for this testing. I'm not sure acceptance is quite right. To me, that implies that if the tests pass then the product is accepted or acceptable. I think the tests I'm describing are more functional that complete acceptance tests. Performance and load testing would be part of acceptance in my mind. I like the term behavior testing, but that is already taken. | |
| Nov 5, 2024 at 10:24 | comment | added | Thomas Owens♦ | @Basilevs The application-level tests don't have to be limited to functionality. Tests could assert performance such as timing or memory consumption, for example. I don't see why acceptance tests can't be automated - there may be specific classes, such as usability or accessibility tests that can only be automated to a limited extent (such as checking against well-defined rules). Tools such as Gherkin use the term "scenario" to refer to an illustration of a business rule that contains the steps to be tested, so I've seen it leak into other testing terminology. | |
| Nov 5, 2024 at 8:55 | comment | added | Basilevs | The better term is functional test. Acceptance tests can't be automated by definition, scenario is a vague term. | |
| Nov 5, 2024 at 1:10 | history | answered | Thomas Owens♦ | CC BY-SA 4.0 |