How to approach Continuous Testing of Cross-Functional Requirements?
summary
Claim: cross-functional requirements (CFRs) are testable continuously by mapping them to five themes—functionality, usability, reliability, performance and supportability—and automating checks at each stage. Examples: run Postman API suites and unit tests for security flows, use visual testing (BackstopJS) and Lighthouse during CI for accessibility and frontend performance, plug in static code analysis (Snyk / dependency scanners, linters) and architecture fitness tests (ArchUnit, JDepend) as gate checks, and run chaos/infrastructure-as-code probes in staging to validate resilience. Continuous feedback happens on every commit.
AI-written summary · about
chapters (9)
- 0:00Introduction and agenda
- 2:17Defining CFRs
- 6:01Understanding CFR vs NFR
- 12:39Continuous testing overview
- 15:57The FURPS model strategy
- 20:40Testing techniques and tools
- 31:08Continuous testing for security
- 36:09Continuous testing for accessibility
- 38:49Key takeaways and conclusion
related talks
16mWhy is Continuous Testing Important?
44mStrategy for Acing Continuous Testing in DevOps
22mTest Automation and Beyond: Implementing Continuous Testing Effectively
34mWhy continuous testing is essential
16mStrategy for Acing Continuous Testing
20mThe Road to Continuous Testing
32mBetter Continuous Testing in DevOps
20mPanel Discussion on Testing