
Funded by the EU. The views and opinions expressed are solely those of the author(s) and do not necessarily reflect the views and opinions of the European Union or the Foundation for the Development of the Education System. . Neither the European Union nor the Foundation for the Development of the Education System are responsible for them.

Project 2023-2-PL01-KA210-VET-000184553 “Automation tester – qualification and certification in vocational education” implemented with the support of the European Union under the Erasmus+ program, key action 2: Small-scale partnerships in the field of vocational education and training (KA210).
Support for teachers and entrepreneurs in cooperation with the education sector.
The project aims to improve the skills of future automation testers and prepare them for work in the IT industry.
Duration: approx. 100 teaching hours + independent study.
Graduate profile:
SDET (Software Development Engineer in Test) who can design a scenario, write code in Python/JS, test API/UI/SQL, and implement it in the cloud.
The course consists of:
STAGE I: Quality Engineer Mindset and Design (15 hours):
Module 1: Test Engineering and Business Analysis
Module 2: Programming Laboratory (Python vs JS)
STAGE II: Backend – Data and API (30 hours):
Module 3: Databases
Module 4: API Testing – Manual and Semi-Automatic
Module 5: API Automation in Python
STAGE III: Frontend – UI and User Experience (30 hours):
Module 6: Web Architecture
Module 7: UI Automation
Module 8: Advanced UI and Mobile
STAGE IV: Engineering of the Future – AI, DevOps, Performance (25 hours)
Module 9: Performance Testing
Module 10: AI in Testing
Module 11: CI/CD and Containerization

Program kursu
- 13 Sections
- 44 Lessons
- 100 Hours
- Introduction1
- Module 1: Test Engineering and Business AnalysisSTAGE I: Quality Engineer Mindset and Design
Before you write a line of code, you need to know WHAT you are testing. Here, we teach thinking, not clicking.5- 2.11.1 Software Development Life Cycle (SDLC): Agile, Scrum. Where does QA fit into all this?
- 2.21.2 Requirements Analysis: Working with User Stories in Jira. Acceptance Criteria as the foundation of testing.
- 2.31.3 Test Design Techniques: Analysis and Implementation of Specification-Based Test Design Techniques in Software Quality Engineering
- 2.41.4 BDD and Gherkin (Behaviour Driven Development): From chaos to precision
- 2.5Test – Automation Tester – Module 160 Minutes15 Questions
- Module 2: Programming Lab (Python vs JS)STAGE I: Quality Engineer Mindset and Design
Before you write a line of code, you need to know WHAT you are testing. Here, we teach thinking, not clicking.5- 3.12.1 Variables and Memory: Data types, variables. Stack vs Heap.
- 3.22.2 Algorithms: Loops (for, while), conditional statements. Bubble sort
- 3.32.3 Functions and Modularisation: The DRY Principle (Don’t Repeat Yourself).
- 3.42.4 Object-Oriented Programming (OOP): Classes, Inheritance, Polymorphism.
- 3.5Test – Automation Tester – Module 260 Minutes15 Questions
- Module 3: Databases (SQL)STAGE II: Backend – Data and API
The invisible but most important part of the system. SQL, REST, Python.5- 4.13.1 Relational Databases: Tables, Keys (Primary/Foreign).
- 4.23.2 SQL in Practice: SELECT, JOIN, WHERE, and GROUP BY queries.
- 4.33.3 Data verification: Checking whether ‘User Created’ has actually been saved in the table.
- 4.43.4 Data verification in NoSQL databases
- 4.5Test – Automation Tester – Module 360 Minutes15 Questions
- Module 4: API Testing – Manual and Semi-Automatic (Postman)STAGE II: Backend – Data and API
The invisible but most important part of the system. SQL, REST, Python.6- 5.14.1 HTTP protocol in quality engineering
- 5.24.2 Postman Pro: Collections, Environment Variables.
- 5.34.3 Scripting in JavaScript and testing APIs in Postman
- 5.44.4 Backend system simulation engineering
- 5.54.5 GraphQL testing challenges for QA engineers
- 5.6Test – Automation Tester – Module 460 Minutes15 Questions
- Module 5: API Automation in Python (Framework)STAGE II: Backend – Data and API
The invisible but most important part of the system. SQL, REST, Python.5- 6.15.1 Architecture and Implementation of Scalable API Testing Frameworks
- 6.25.2 Advanced validation and data architecture with Pydantic V2
- 6.35.3 Advanced authorisation architecture in API testing
- 6.45.4 Reporting: Generating HTML reports (Allure).
- 6.5Test – Automation Tester – Module 560 Minutes15 Questions
- Module 6: Web ArchitectureSTAGE III: Frontend – UI and User Experience
User simulation. Playwright as the main tool.4 - Module 7: UI Automation (Playwright Python)STAGE III: Frontend – UI and User Experience
User simulation. Playwright as the main tool.6- 8.17.1 Playwright vs Selenium: Why the modern web requires new tools.
- 8.27.2 Interactions in UI testing: Forms, Modals, Shadow DOM, iFrames.
- 8.37.3 Page Object Model (POM) pattern: Professional test code architecture.
- 8.47.4 Pytest-BDD
- 8.57.5 Accessibility automation in the Playwright ecosystem
- 8.6Test – Automation Tester – Module 760 Minutes15 Questions
- Module 8: Advanced UI and MobileSTAGE III: Frontend – UI and User Experience
User simulation. Playwright as the main tool.3 - Module 9: Performance TestsSTAGE IV: Engineering of the Future – AI, DevOps, Performance
Elements that distinguish a Senior from a Junior.4 - Module 10: AI in Testing (QA 2.0)STAGE IV: Engineering of the Future – AI, DevOps, Performance
Elements that distinguish a Senior from a Junior.4 - Module 11: CI/CD and ContainerisationSTAGE IV: Engineering of the Future – AI, DevOps, Performance
Elements that distinguish a Senior from a Junior.6- 12.111.1 Docker: Containerisation of tests
- 12.211.2 GitHub Actions: Building a pipeline. Automatically running tests after git push.
- 12.311.3 Strategies for running tests in CI CD
- 12.411.4 Code working strategies and code review in test automation
- 12.511.5 Observability in quality engineering
- 12.6Test – Automation Tester – Module 11100 Minutes25 Questions
- Additional materials1
