The Framework That Knows Its Bugs
summary
A small Java system hooks automated tests to JIRA so the framework reads a presaved JIRA filter, parses issue fields and a custom test‑ID field, and disables tests whose IDs match low‑priority active defects before execution; uses TestNG annotation transformer, REST calls via JIRA REST API, RestAssured and Jackson; demo shows the whole implementation in four classes, reports ignored methods and can auto‑comment or reopen tickets on test failure — it runs in CI and demonstrably keeps builds green while surfacing repeat offenders for cleanup.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:12Automated tests in agile
- 3:17Repeating test failures in CI
- 5:02JIRA data for test failures
- 7:07Linking JIRA defects to tests
- 9:40Filtering defects for automation
- 12:13Fetching defects via REST API
- 13:16Disabling tests with TestNG
- 15:02Live demo
- 19:44Updating JIRA on test results
- 25:08Risks and mitigation
- 26:58Additional opportunities
- 29:31Conclusion and key takeaways
- 30:34Q&A
related talks
35mEx Machina: The Framework That Knows its Bugs
41mThe Tester’s Guide to Quality
47mFrom Bugs to Brilliance: Testing Toolbox in Action
46mModern Testing Tools for Java Developers
49mTestCases as Code
05mTaming the Testing Beast
41mSoftware Architecture — Yes, on Tests
57mModern Testing Tools for Java Developers