Practice
QA Trainers for Software Testers
Small apps with requirements. In Test Design trainers, you design tests with a test design technique and compare them with the reference solution. In SDLC trainers, you work through the development cycle with the team — from requirements to release.
Learn the topic: Test Design Techniques and PracticeClient-Server and HTTP for TestersDevTools for TestersQA Tester Interview Questions
- Onboarding
1. Who Is Who: Roles in an IT Team
Sandra, an HR specialist, explains who works in an IT team, which business stakeholders bring requirements, and what HR does.
Start - Onboarding
2. Meeting the Team Lead
You have joined the team as a QA intern. The team lead explains how it works: first we learn a little, then we practise.
Start - Onboarding
3. Lunch with the QA Team
Kadri, your mentor, takes you to lunch with the testers: how each of them joined, who writes automated tests and who is still learning, and why it’s fine to ask for help.
Start - Client-Server
1. How Modern Applications Work
Kadri, your mentor, explains why an application is a system of many components and why a tester needs to understand the architecture for integration and system testing.
Start - Client-Server
2. The GET Method: Loading the Catalogue
How the client, the server, and the database exchange data, using an online shop loading its catalogue.
Start - Client-Server
3. The POST Method: Adding a Product
How an administrator adds a product to the catalogue: a POST request, the request body, code 201, and a new row in the database.
Start - Client-Server
4. The PATCH Method: Changing a Price
How an administrator changes part of a product’s data: a PATCH request with the price only, code 200, and an updated column in the database.
Start - Client-Server
5. The PUT Method: Replacing a Product
How an administrator replaces a product completely: a PUT request with the full data, code 200, and how PUT differs from PATCH.
Start - Client-Server
6. The DELETE Method: Deleting a Product
How an administrator deletes a product from the catalogue: a DELETE request, the product number in the address, code 204, and a deleted row in the database.
Start - Client-Server
7. Response Codes: 401, 404, 405 and an Empty List
How the server reports problems: 401 without logging in, 405 for a method that is not allowed, 404 when deleting a product that does not exist, and 200 OK with an empty list.
Start - Client-Server
8. Client-Server in Real Projects
What the system looks like when there are many clients: a load balancer, several backends and databases, a monolith and microservices.
Start - Client-Server
9. Summary: Client and Server
The final test quiz of the whole client-server introductory series: check how well you have absorbed the material. A cheat sheet on methods and response codes comes first, followed by 23 questions on every topic covered.
Start - Client-Server
10. Self-study: A CRUD Diagram of a Todo App
Reinforce the series: draw a “Client → Server → Database” diagram in Excalidraw for six actions in a Todo app — the method, the request, the response and the changes in the table.
Start - Postman
1. Meet Postman: Who Else Can Be a Client
What an API and an endpoint are, why the client isn’t only the browser and why a tester needs Postman. Plus: how path parameters differ from query parameters, and what’s in the Postman window.
Start - DevTools
1. Meet DevTools
What DevTools are, how to open them, how they differ from Postman and why a tester needs the Network and Application tabs.
Start - DevTools
2. DevTools: the Network Tab
Press the buttons of a mini interface: get the list, create and delete a product. See which requests and responses appear in Network.
Start - DevTools
3. DevTools: the Application Tab
Where the site keeps the GDPR consent cookie, how to delete it to see the banner again, and how the cookie gets into request headers.
Start - Test Design
1. Boundary Values: Driving Licence
Equivalence partitioning and boundary value analysis on an age check.
Start - Test Design
2. Boundary Values: Username
Equivalence partitioning and boundary value analysis for a text field: length and allowed characters.
Start - Test Design
3. State Transition Testing: Sign-in Lockout
State transition testing on a lockout after three wrong passwords.
Start - Test Design
4. Boundary Values: Order Total Discount
Equivalence partitioning and boundary value analysis on a three-product cart with an order total discount.
Start - Test Design
5. State Transition Testing: Flight Booking
State transition testing on a seat booking with a payment timer.
Start - Test Design
6. Error Guessing: Creating an Account
Error guessing on a date of birth field with manual input and a calendar.
Start - Test Design
7. Test Design: Pick the Test Data
Five short cases: read the requirement and pick the test data set using equivalence partitioning or boundary value analysis.
Start - SDLC
1. Exploratory Testing: Meeting Room Booking
Exploratory testing on a meeting room booking app.
Start - SDLC
2. Smoke, Retest and Regression: Payment Form
Smoke testing, retesting, new feature testing, and regression testing on adding an instalment payment option to a payment form.
Start - SDLC
3. Smoke and Regression Testing: Sign-in Methods
Add Mobile-ID, run smoke checks, and find two regression defects in existing sign-in methods.
Start - SDLC
4. Smoke, Retest and Regression: Promo Code
Smoke testing, retesting, new feature testing, and regression testing on adding a discount promo code to a payment form.
Start - SDLC
5. End-to-End Integration Testing: Pay in Instalments
Smoke testing, new feature testing, retesting, system end-to-end testing, and regression testing on connecting a real external instalment payment service.
Start - Git and GitHub
1. Git and GitHub in an IDE: From a Commit to a Pull Request
What a commit, a local repository and GitHub are. Add a test case to the team’s repository with IDE buttons: Clone, a new branch, Commit, Push, a Pull Request, review, Merge and Update Project.
Start - Git and GitHub
2. Reviewing a Pull Request on GitHub
Become the reviewer: check the code against the requirements in the Files changed tab, leave polite line comments, request changes and approve the PR after the author’s new commit.
Start - Interview: Hard Skills
1. QA Basics and the Tester’s Role
Quiz: testing vs QA, test levels, smoke and regression, positive and negative checks, incomplete requirements.
Start - Interview: Hard Skills
2. Bug Report and Arguing with a Developer
Quiz: bug report structure, severity and priority, steps to reproduce, environment and the “it works for me” reply.
Start - Interview: Hard Skills
3. Practical Interview Questions
Quiz: how to test a login form, what to do when time is short, retest and regression, API and Postman, test cases, test report and SQL.
Start - Interview: Hard Skills
4. Client-Server at an Interview
A simple quiz: client and server, request and response, HTTP and HTTPS, methods, codes 404 and 500, headers and body, DevTools.
Start - Interview: Teamwork
1. Scrum, Agile and Teamwork
Quiz: Agile and Scrum, sprint, roles, Daily and retrospective, Definition of Done, Sprint Review, Backlog Refinement, the QA role in a sprint and communication in a team.
Start - Interview: Teamwork
2. Development Processes: SDLC, retro, code freeze
Quiz: SDLC, retrospective, code freeze, acceptance criteria, sprint planning, test environments, CI and a bug on production.
Start - Interview: Teamwork
3. Team Roles and Collaboration
Quiz: analyst, developer, DevOps, designer and test lead: whom to go to with which question, how to report a bug and who is responsible for quality.
Start