Building an Automated Test System from Scratch
summary
A small company built an automated testing pipeline in about four months using Jenkins for CI, eslint/phpcs linters, unit frameworks (Jasmine, PHPUnit, Erlang eunit), REST tests in Java with JUnit, Allure for reports and apidog for API docs. The practical approach prioritized making the product testable, enforcing a minimal critical linting set, documenting REST APIs first, covering key flows with short smoke tests, and keeping test reports informative and isolated.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:52Automated testing plan
- 3:34Code parsing for testability
- 6:47Linting tool selection
- 8:14Code documentation importance
- 10:03Documenting critical components
- 11:28Documentation from comments
- 13:15Tester's role in unit tests
- 14:57Test coverage prioritization
- 16:23Test infrastructure setup
- 17:29Automated testing pros and cons
- 21:24REST API testing and reports
- 22:50Automated testing in startups
- 24:17Web UI testing tools
- 25:43Testing test code automation
- 26:47Report structure and importance
- 30:41CI/CD testing example
- 32:04Summary
related talks
18mEffective Test Automation Framework Design
45mTesting the web without testers — success or failure
38mScaling Automated Testing & Architecture from Startup to Enterprise
50mFrontend-as-a-Service Automated Testing: Layers and CI Pipelines
28mBuilding an automated testing suite...
18mAutomation Lessons Learned
13mFewer Tools, More Impact: An Automated Testing Strategy for Scale-Up
52mHow to win with automation and influence people