Talk:Test automation
Template:WikiProject banner shell Template:Tmbox User:ClueBot III/ArchiveThis
Requirements Testing
I would like to propose that this article is enhanced to include the topic of Requirements Test Automation. As I have a conflict of interest, I would ask someone else to vet and consider it's inclusion. https://ceur-ws.org/Vol-2207/IWSM_Mensura_2018_paper_11.pdf and the tool that does the requirements test automation is <<linkspam redacted>> Thank you. Colinrhammond (talk) 10:06, 4 December 2022 (UTC)
- No, Colin. We're not going to help you advertise. - MrOllie (talk) 21:52, 23 January 2023 (UTC)
- Pretty sure that requirements testing is not inherently connected to test automation and therefore doesn't belong in this article. It might be a type of software testing. Stevebroshar (talk) 11:39, 14 April 2024 (UTC)
Lots of issues
Much of the info in sentences is correct, but many section headers are misleading if not wrong. How info is organized is also info.
Article conflates test automation with software testing in general. For example, 'regression testing' is not an approach to test automation. Regression testing is a particular kind of software testing. A regression test is much easier and cheaper to run if it's automated. So, if one wants to connect these two concepts, it could be as a value/plus/advantage. Most if not all of the things under approaches are not that. They are kinds of software testing.
I wouldn't call TDD or continuous testing 'methodologies'. They are smaller than that term implies.
Test automation is not inherently required for continuous delivery. It's wise to test before delivering. Critical is way too judgmental.
predicted? it's called expected.
I'll get to this stuff at some point. Stevebroshar (talk) 11:37, 14 April 2024 (UTC)