Software Architecture — Yes, on Tests
summary
Describes a modular testing architecture built around a small central Java core with interchangeable interfaces, replacing brittle monolithic suites. Uses FitNesse, JMeter, Selenium/Nightwatch and RestAssured; tests are stored as JSON test files or CSV/text so new tests can be written in about half a day without Java debugging. Presents concrete refactors (e.g., 60 lines of Java reduced to one JSON case), Bamboo/JUnit reporting, and claims Nightwatch+RestAssured cut about 80% of reuse work when changing technologies.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 3:41QA role in development
- 7:15Waterfall to Agile shift
- 11:17Three early mistakes
- 15:12Systematic modular approach
- 18:46Backend architecture
- 25:13Steps to freedom
- 30:58Summary and best practices
- 33:53Q&A
related talks
47mMicroservices Testing with Java
51mTesting Software Architecture
46mHow to Create an Architecture for Web Test Automation
43mUnit Test Your Java Architecture With ArchUnit
58mTesting Software Architecture
57mModern Testing Tools for Java Developers
46mModern Testing Tools for Java Developers
51mA testable architecture