TestCases as Code
summary
Presents a system treating test cases as code using Java annotations and a Gradle plugin to integrate with TestRail and Jira. The implementation stores test metadata in the repo, lets CI generate TestRail test cases and runs that combine automated and manual checks, posts results back, and computes coverage per epic/story. A prototype running since July 2018 on a real project shows this approach narrows the automation/manual testing gap.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:14Test cases in code
- 4:13Traditional test issues
- 7:27Automation limits
- 10:41Classic flaws
- 13:53Code storage benefits
- 16:41New approach needs
- 21:24Checklists vs test cases
- 24:15Java test structure
- 27:27Manual checks in automation
- 30:17Test generation plugin
- 33:53Plugin context handling
- 36:24Jira integration
- 38:31Auto test-run in Jira
- 40:20Manual check distribution
- 42:05Reporting and coverage
- 44:35Challenges and future
- 46:19Team adoption results
- 47:43Test management experiments
related talks
28mIntegration of automated tests with testing tools
50mTest Cases Are Dead. Long Live Test Cases!
36mThe Framework That Knows Its Bugs
41mCode Review Techniques for Test Automation
35mEx Machina: The Framework That Knows its Bugs
01h 01mHow to (Not) Use Testers Properly
41mThe Tester’s Guide to Quality
51mTest-Driven: from Zero to Hero