SeleniumLab

Course → 3 · Professional QA engineering → Test Design Techniques

3 · Professional QA engineering

Decision tables and state transition

18 min · Module 16

Decision tables map combinations of conditions → actions (e.g., role + status → allowed transitions).

State transition testing walks statuses: Open → In progress → Resolved (and illegal jumps).

Lab: try legal and illegal status updates on a ticket; on some releases status save is broken—report it.

Example / notes

# State model (HelpDesk)
# open -> in_progress -> resolved
# Also test: resolved -> open (if allowed), and blocked transitions

Practice in Lab: /lab/app/tickets/

Log in to track progress / take quizzes

← Equivalence partitioning and BVA Pairwise and exploratory testing →

Modules in this track

15. QA Foundations — Strategy & Planning
- Writing a test strategy
- Test planning and estimation
16. Test Design Techniques
17. API & Contract Testing
- HTTP API testing fundamentals
- Contract and schema testing
18. Performance Testing Basics
- Performance concepts and SLOs
- Designing a minimal performance check
19. Security Testing Basics
- Auth, sessions, and authorization
- OWASP-minded checks for web apps
20. Accessibility Testing
- Accessible by design checks
- Automated a11y smoke
21. Mobile Testing
- Mobile web quality risks
- Native apps and device farms (overview)
22. CI/CD, Quality Gates & Environments
- Pipelines and quality gates
- Environments and progressive delivery
23. Test Data, Environments & Observability
- Test data management
- Observability for QA
24. Soft Skills — Stakeholders, Mentoring, Metrics
- Stakeholder communication
- Mentoring and quality metrics/OKRs
25. Career & Process — Agile, Compliance, Senior Bar