No QA resources? You can still deliver a quality website
summary
Shows how a lean team delivers a stable site by naming who owns each QA task, writing a minimum testing checklist (smoke tests across dev/stage/prod), and timeboxing work so high‑risk items get covered first. Recommends splitting planning vs execution, logging bugs so you can say “we found 23 issues,” and automating only stable regressions with tools like WAVE, axe, Selenium/Protractor and visual runners (Percy, Ghost Inspector, Applitools). Includes sample test plans, test data advice, and a checklist of tests to run when no dedicated QA is available.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker background
- 5:29What is quality assurance
- 10:27Distributing QA tasks without a dedicated person
- 14:05Why we test and test planning basics
- 21:25Prioritizing minimum testing checklist
- 25:42Test strategy and V model planning
- 31:32Who does testing and empathy in testing
- 36:35Test automation realities and tools
- 41:12Convincing management to invest in QA
- 46:10Accessibility testing tools and persuasion
- 55:55Q&A and closing remarks
related talks
41mLife Without QA
21mEstablishing Quality Assurance in Startup environment
53mBest-Practice Quality Assurance for Small Teams
45mSame Old Story: Foundation of the QA Department. Tips and Tricks
36mWhy a Growing Company Needs a Growing QA Team
53mIs having a QA a symptom of a dysfunctional team?
43mLean QA: Automation, Monitoring, Experiments
46mQA to QE: Scaling Quality with Ownership, Code, and Culture