How to Befriend QA and Development by Storing Tests in Code
summary
Describes using a single code-based test storage to bridge QA and development by keeping test cases alongside application code. Explains reducing manual entry into test-case tools, correlating developer-written unit tests with end-to-end tests, and using code practices to make coverage and overlap between test types visible and manageable.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:17Traditional QA problems
- 7:57Allure and tests in code
- 13:35Exporting tests to Allure
- 19:45Export system architecture
- 26:06Team benefits
- 34:14Q&A
related talks
01h 01mHow to (Not) Use Testers Properly
44mTest Automation as a Development Team
45mSame Old Story: Foundation of the QA Department. Tips and Tricks
24mDemystifying Code Through Testing
52mCreating a QA/DEV Collaborative Testing Strategy
53mEssential Tools for Improving Test Code Quality
41mLife Without QA
23mWhy testing is also a developer's problem