The tech lead of a QA team at an insurance company gets a question from HR before budget planning: “How many people do you want to send for ISTQB next year?” There are eight testers on the team. Three hold the Foundation certificate, one holds an Advanced one. The two best automation engineers have none and say they do not need one. A week earlier, sales reported that a large tender requires at least half of the testing team to be ISTQB certified.
The tech lead has to answer three questions at once: which certifications make sense in 2026, what certifying a team really costs, and whether the spend will deliver more than a formal tick in a tender. Opinions in the industry are polarised — from “no ISTQB, no tester” to “a definitions quiz that says nothing about skill”.
Below, we lay out the facts: the current ISTQB certification paths, exam formats, 2026 prices in Poland and a cost model for a team of eight, with open assumptions so you can plug in your own numbers. Amounts are in Polish złoty; where helpful, we add an indicative euro value at 4.30 PLN per EUR. At the end, we show how to plan a certification programme that supports the team’s goals rather than filling a box in the annual review.
What is ISTQB and why did it become the standard for tester certification?
ISTQB (International Software Testing Qualifications Board) is a not-for-profit organisation founded in 2002 that creates syllabi and exam standards for software testing. It does not run training or most exams itself — national member boards and accredited exam providers do. In Poland the member board is SJSI (Stowarzyszenie Jakości Systemów Informatycznych), which has been active for more than 20 years and is known in the ISTQB context as the Polish Testing Board.
The scale is significant. According to ISTQB, by May 2025 it had administered more than 1.5 million exams and issued more than 1.1 million certifications in over 130 countries, with 69 member boards running the scheme. The certificate is identical regardless of where it is earned, which matters for distributed teams and projects for foreign clients.
Why ISTQB rather than another certificate? For three reasons. First, the syllabi are public and free — anyone can download them and see what the exam requires. Second, ISTQB maintains a glossary of testing terms that has, in practice, become the industry’s common language: “test case”, “test condition” and “risk-based testing” mean the same in Warsaw, Bangalore and Munich. Third, the certificates are recognised by employers and by buyers in tenders, which creates a network effect that competing schemes find hard to break.
It is also worth knowing what ISTQB does not cover. It certifies individuals, not organisations — the maturity of a company’s whole test process is assessed with other models, such as TMMi. It does not certify skills in specific tools — that is the domain of tool vendors and cloud platforms. Nor does it cover requirements engineering, which has its own scheme, IREB; in Poland, SJSI accredits training in both. For a QA team these certifications complement each other: ISTQB provides a shared foundation of testing knowledge, while tool and domain certificates provide the skills a specific project needs.
None of this makes ISTQB the only path for a tester’s development. It does explain why the name comes up more often than any other in discussions about quality standards in software testing.
Which ISTQB levels and certification paths apply in 2026?
The ISTQB portfolio is organised along two dimensions: levels (Foundation, Advanced, Specialist, Expert) and streams (Core, Agile, Specialist). In 2026 the key elements look like this:
| Level | Certifications (selected) | For whom | Prerequisites |
|---|---|---|---|
| Foundation | CTFL v4.0 — Certified Tester Foundation Level | Every tester, as well as developers and analysts | None |
| Advanced (Core) | Test Analyst (CTAL-TA) v4.0, Technical Test Analyst (CTAL-TTA) v4.0, Test Management (CTAL-TM) v3.0, Test Automation Engineering (CTAL-TAE) v2.0 | Experienced testers, leads, automation engineers | CTFL |
| Advanced (Agile) | Technical Agile Tester and other Agile stream modules | Testers in agile teams | CTFL (some modules have extra prerequisites) |
| Specialist | AI Testing (CT-AI) v2.0, Testing with Generative AI (CT-GenAI) v1.1, Performance, Security, Mobile, Usability, Acceptance, Automotive, Game Testing and others | Testers specialising in an area | CTFL |
| Expert | Assessing Test Process, Implementing Test Process Improvement | Test process architects, consultants | Advanced plus documented experience |
Several recent changes matter for planning. Foundation Level 4.0, released in 2023, replaced version 3.1 and clearly shifted the emphasis towards testing in agile and DevOps teams, risk-based testing and the tester’s role across the whole development life cycle. Advanced Test Analyst 4.0 was released in May 2025; the previous version retired in English on 16 May 2026 and retires in other languages on 16 November 2026. Technical Test Analyst 4.0 was formally released in November 2025. Testing with Generative AI was approved in July 2025, and a minor update, version 1.1, followed in April 2026.
One rule matters for the budget: Foundation, Advanced and Specialist certificates are valid for life, regardless of the syllabus version under which they were earned. A tester with a CTFL 3.1 certificate from 2019 does not need to retake the exam. The exception is the Expert Level, whose certificate is valid for 7 years. Certification is therefore a one-off cost — but it also means an old certificate does not guarantee knowledge of the current syllabus.
What does the ISTQB Foundation Level 4.0 exam look like and how much preparation does it need?
The Foundation Level 4.0 exam has 40 multiple-choice questions in 60 minutes. Each question is worth one point, there is no negative marking, and the pass mark is 65% — 26 correct answers. Candidates taking the exam in a language other than their native one get 25% extra time, or 75 minutes. The exam is available in many languages, including Polish.
Questions test three cognitive levels: K1 (remember — for example a definition from the glossary), K2 (understand — compare, explain or classify concepts; most questions sit here) and K3 (apply — for example deriving boundary values or completing a decision table). K3 questions are the closest to practice, and they are where candidates who studied only definitions most often lose points.
Advanced exams are considerably harder. Test Analyst 4.0 has 45 questions worth 78 points in total, 120 minutes, with a pass mark of 51 points (65%). Questions are scenario-based: you analyse a description of a project situation and choose the right technique or decision rather than recall a definition.
How much preparation is needed? Accredited Foundation Level training usually takes 3 days. For a tester with a year of practice, that is often enough when combined with a dozen or so hours of self-study with the syllabus and the sample exams ISTQB publishes for free. Someone with no testing experience — a developer or an analyst, for example — usually needs more time because the terminology is new to them.
In our model we assume 5 working days per person for Foundation (3 days of training, 2 days of self-study) and 8 days for Advanced (3 days of training, 5 days of self-study). These are cautious assumptions — it is better to plan more time than to have people sitting the exam twice.
How much do ISTQB exams and training cost in Poland in 2026?
Exam prices are set by the member board or the exam provider. According to the current SJSI price list:
| Exam | Net price | Approx. EUR |
|---|---|---|
| Foundation Level (CTFL) | PLN 850 | EUR 200 |
| Agile Tester, Acceptance Tester | PLN 850 | EUR 200 |
| Advanced: Test Analyst, Technical Test Analyst, Test Manager, Technical Agile Tester | PLN 1,150 | EUR 270 |
| Specialist: Test Automation Engineer, Security, Performance, Mobile, AI Tester, Generative AI Testing, Usability, Automotive, Game | PLN 1,150 | EUR 270 |
| Expert: Assessing Test Process, Implementing Test Process Improvement | PLN 3,000 | EUR 700 |
Other accredited exam providers in Poland charge similar amounts — in the offers we checked, the Foundation Level exam cost from PLN 780 net (online) to PLN 900 net (in person). It is worth comparing, especially when ordering exams for several people at once. Prices in other countries differ, as each member board sets its own.
Training costs more than the exam. Accredited Foundation Level 4.0 training cost from about PLN 1,000 net (e-learning) to about PLN 1,550 net (3 days live online with a trainer) in the offers we checked. Advanced Test Analyst training cost about PLN 3,200 net for 3 days. Training is not mandatory: you can sit the exam after self-study. For experienced testers that is a realistic option; for beginners, rarely a good idea.
Two practical budget notes for companies in Poland. First, some courses are listed in the Polish Agency for Enterprise Development (PARP) training database with public co-funding — when at least 70% of a training service is publicly funded, it is VAT-exempt. Second, the SJSI price list has no separate retake fee, so a retake needs to be budgeted as a full exam.
What does certifying a whole QA team cost and when does it pay back?
Back to the team from the introduction. Assume the tech lead certifies all eight people: six take Foundation Level, and two experienced people take Advanced (one Test Analyst, one Test Automation Engineering).
Assumptions you can replace:
- Cost of one hour of a QA team member’s work: PLN 120 — the middle of the range for a mid-level tester in our 2026 body leasing rate benchmark (PLN 100–140 an hour). The full employer cost per productive hour of an employee at a similar level falls in the same range.
- Foundation: exam PLN 850, training PLN 1,547, 5 working days (40 hours).
- Advanced: exam PLN 1,150, training PLN 3,200, 8 working days (64 hours).
- Retake reserve: one retake at Foundation and one at Advanced — PLN 2,000.
| Item | Per person | People | Total |
|---|---|---|---|
| Foundation — exam and training | PLN 2,397 | 6 | PLN 14,382 |
| Foundation — working time (40 h × PLN 120) | PLN 4,800 | 6 | PLN 28,800 |
| Advanced — exam and training | PLN 4,350 | 2 | PLN 8,700 |
| Advanced — working time (64 h × PLN 120) | PLN 7,680 | 2 | PLN 15,360 |
| Retake reserve | — | — | PLN 2,000 |
| Total | PLN 69,242 |
The key takeaway from this table: 64% of the cost of certification is working time, not fees. The cash outlay is PLN 25,082 (about EUR 5,800), but the team spends 368 hours preparing — hours not spent testing. A budget that counts only exam and training invoices understates the cost almost threefold.
The scale of the programme matters a lot. A minimal variant — Foundation Level only for the three people without a certificate, and no Advanced — costs PLN 21,591, less than a third of the full programme. Conversely, at a higher hourly cost, say PLN 150 for a team dominated by automation engineers, working time alone in the full variant rises from PLN 44,160 to PLN 55,200. That is why it pays to calculate at least two variants before deciding.
When does it pay back? The annual labour cost of a team of eight, at 1,696 productive hours per person and PLN 120 an hour, is about PLN 1.63 million. Certification is 4.25% of that in the first year. Because certificates are valid for life and the knowledge keeps its value for several years, it is fairer to spread the cost over three years — then it is 1.42% a year, or about 24 hours, roughly 3 working days per person per year.
So the payback question is concrete: will a shared language, better test design and conscious risk management save each team member at least 3 days a year? In a team that regularly argues about what a “test case” is versus a “scenario”, or lets production defects through because boundary values were skipped — almost certainly. In a mature team with a strong engineering culture — not necessarily. And if certification is a condition for bidding on a tender, the calculation is different: what counts is the contract value, not the time saved.
What does an ISTQB certificate say about a tester, and what does it not?
An ISTQB certificate confirms one thing: that a person knows and understands the syllabus content at a given level. That is valuable information, but narrower than many job ads assume.
What a Foundation Level certificate says:
- The tester knows standard terminology and understands the test process, from planning to test completion.
- They know the basic test design techniques: equivalence partitioning, boundary value analysis, decision tables and state transition testing.
- They understand risk-based testing, test levels and types, and the tester’s role in an agile team.
- They were able to prepare for and pass an exam — which shows a certain discipline.
What the certificate does not say:
- Whether the tester can write automated tests and maintain a framework — Foundation does not test this, and even Advanced TAE tests knowledge of automation architecture rather than programming ability.
- Whether they can find an important bug in an unfamiliar application within an hour — a practical skill developed through exploratory testing and experience.
- Whether they understand the business domain — insurance, banking, logistics.
- Whether they communicate well with developers and the business, which in practice determines a tester’s effectiveness at least as much as technical knowledge.
The conclusion is simple: a certificate is evidence of knowledge, not of skill. It does not replace a practical task in recruitment or an assessment of project work. It does help in two situations: when you need to check quickly whether a candidate knows the basics, and when a team needs a shared vocabulary. We cover this in more detail in our article on how to hire a QA developer in 2026.
When does certifying a team make real business sense?
Our experience delivering testing projects for clients in Poland and abroad shows five situations in which certifying a team has a strong case.
1. Tenders and contractual requirements. Public buyers and large companies in financial services, energy and telecoms often require a certain number of testing team members to hold ISTQB certificates — usually Foundation, and Advanced Test Manager for the test lead role. Here the certificate is not an investment in knowledge but a condition of market entry. The calculation is simple: compare the cost of certification with the value of the contracts you cannot access without it.
2. Regulated industries. In banking, insurance, healthcare and automotive, auditors and regulators expect a documented test process. A team that knows the standard ISTQB approach to test planning, traceability and reporting more easily produces documentation that passes an audit. Certificates are also one form of evidence of staff competence.
3. Distributed or mixed teams. When testers come from different companies, countries or providers — for example in a staff augmentation model — shared terminology shortens onboarding and limits misunderstandings. “Design tests for this field using boundary value analysis” then means the same thing to everyone.
4. Building a team from scratch or growing fast. Juniors and people moving into testing from other roles gain the most from Foundation Level: they get a structured map of the field instead of picking knowledge up at random. It is one of the cheapest forms of structured onboarding.
5. A change of role. A tester promoted to test lead will benefit from Advanced Test Management, and a manual tester moving into automation from Test Automation Engineering. Here the certificate structures the transition to the new role, and the exam is a goal that motivates systematic learning.
There are also situations where certification has a weak case: an experienced team of automation engineers with no formal requirements, a team in which developers do the testing, or a company that treats the certificate as a substitute for real development — without projects, mentoring and time to practise.
Which ISTQB certificate should you choose for which role on the team?
The most common mistake in certification programmes is sending everyone to the same exam. The table below shows how to match the path to the role:
| Role on the team | Base certificate | Next step | When it is worth it |
|---|---|---|---|
| Junior tester / person from another role | Foundation Level 4.0 | Agile Tester or Acceptance Tester | Always — the best value for money |
| Manual tester (mid, senior) | Foundation Level 4.0 | Advanced Test Analyst 4.0 | When responsible for test design and requirements analysis |
| Automation engineer / SDET | Foundation Level 4.0 | Test Automation Engineering 2.0 or Technical Test Analyst 4.0 | When designing automation architecture, not just writing scripts |
| Test lead / QA manager | Foundation Level 4.0 | Advanced Test Management 3.0 | When responsible for test strategy, budget and reporting |
| Performance or security tester | Foundation Level 4.0 | Specialist: Performance Testing or Security Testing | When it is the main area of work |
| Tester of AI products | Foundation Level 4.0 | AI Testing 2.0 or Testing with Generative AI 1.1 | When testing AI systems or introducing AI into the test process |
| Developer, analyst, product owner | Foundation Level 4.0 (optional) | — | When the team wants a shared quality language across roles |
Note the last row. Foundation Level is not a certificate for testers only. In teams where everyone owns quality, not just the QA department, Foundation Level training for developers and analysts is sometimes more effective than another certificate for a tester who already knows the basics.
Are the ISTQB certifications on AI and automation worth attention in 2026?
This is the area where ISTQB is changing fastest, and it is worth following regardless of any certification decision.
AI Testing (CT-AI) v2.0 is about testing systems that themselves use machine learning: how to test a model that has no deterministic outputs, how to assess training data quality, how to measure bias and robustness. It is a certificate for testers working on AI-based products.
Testing with Generative AI (CT-GenAI) has a different scope: it is about using large language models in a tester’s work. It covers prompt engineering for testing, the risks of using AI, test infrastructure based on generative AI and adopting AI in an organisation. The syllabus was approved in July 2025, and accredited training must last at least 13.6 hours. For teams starting to use AI to generate test cases or test data or to analyse results, it is one of the most practical certificates in the portfolio today.
Test Automation Engineering (CTAL-TAE) v2.0 sits in the Core stream at the Advanced level. It covers test automation architecture: choosing an approach, designing layers, reporting, maintenance and integration with the CI/CD pipeline. It does not teach a specific tool — which is its strength, because tools change faster than principles. If you are planning an investment in automation, see also our calculation of how much test automation costs in 2026.
Changes driven by AI raise the value of certificates that teach risk thinking and test design and lower the value of knowledge about operating specific tools. A language model can generate dozens of test cases in seconds today. Judging which of them are needed and which risks were missed is still the job of a person who understands the techniques in the syllabus. We discuss how AI is changing the tester’s profession in our article on whether AI will replace software testers.
How can a team use ISTQB syllabi without certifying everyone?
One of the most underrated features of ISTQB is that the syllabi, the glossary and the sample exams are free. A team can draw on them without paying exam fees — and certify only where a certificate has formal value.
Four practices that work in QA teams:
- A team glossary based on the ISTQB glossary. Instead of arguing over definitions, the team adopts ISTQB terminology as its reference and documents only the deviations. A few hours of work that save many misunderstandings in reports and reviews.
- Internal sessions following the syllabus chapters. A certified person runs a one-hour session every two weeks on one topic — for example boundary value analysis applied to the current project. Within a quarter, the team covers the key techniques with no training spend.
- Sample exams as a diagnostic. A sample exam taken anonymously by the whole team shows where the gaps are. It is a better basis for a development plan than self-assessment.
- Document templates aligned with the ISTQB process. A test plan, test report and test strategy based on the syllabus structure make audits and project handovers between teams easier.
In this model, certification becomes a complement rather than the only form of development. You certify the people whose certificate is formally required (tenders, audits, lead roles), and the rest of the team benefits from the same knowledge at a fraction of the cost.
How should you recruit and assess testers with and without an ISTQB certificate?
Requiring an ISTQB certificate in a job ad is a decision with consequences. It narrows the candidate pool without guaranteeing quality. Our experience recruiting testers points to three rules.
Use the certificate as a filter, not an assessment criterion. If a client or tender requires a certificate, apply it as a formal condition. If not, treat it as a plus, not a requirement. A tester with five years of experience testing payment systems and no certificate is usually more valuable than someone with an Advanced certificate and one year of experience.
Test what the certificate does not. A good recruitment task for a tester includes a short application or a specification excerpt and a request to design tests, identify risks and report the bugs found. Within an hour you will see whether the candidate applies test design techniques in practice or only knows their names.
Ask about the version and the context. A CTFL 2.x certificate from a decade ago and a CTFL 4.0 from last year are formally the same level but different content — version 4.0 puts much more emphasis on working in agile and DevOps teams. It is also worth asking how the candidate has used the knowledge from certification in a project. A concrete answer says more than the document itself.
On the development side, a certificate can be part of a career path — for example a condition for promotion to test lead, combined with an assessment of project work. It should not be the only criterion. If you are building a QA team faster than recruitment allows, a good alternative is software tester rental — specialists with verified skills and the certificates a project requires.
How do you prepare a team to pass the exam first time?
Every retake costs another PLN 850 or 1,150 and, more importantly, more days of preparation. That is why preparation deserves the same care as choosing the certificates. Our experience points to several practices that clearly improve first-time pass rates.
Accredited training or self-study? For Foundation Level, experience decides. A tester with several years of practice who uses test design techniques daily will usually manage with the syllabus, the glossary and sample exams. A junior or someone from another role benefits from a trainer-led course, which provides a structured map of the field and answers to questions a textbook cannot. For Advanced, training is a good choice almost always — scenario-based questions require practice in case analysis that is hard to gain alone.
The syllabus is the source of truth. Exam questions rely solely on the syllabus and the ISTQB glossary. Knowledge from other sources, even when correct, sometimes contradicts ISTQB definitions in the details — and in the exam, the syllabus definition is what counts. This is a common reason experienced testers who “know better” from practice fail.
Sample exams under exam conditions. ISTQB publishes official sample exams with explanations of the answers. Taking at least two within the time limit, then analysing every wrong answer, is the most effective form of revision. A score clearly above the 65% pass mark in a practice run is a good sign of readiness.
K3 questions need practice. Deriving equivalence partitions and boundary values or completing decision tables must be practised on examples, ideally from the current project. Reading the chapter is not enough.
Protected time in the calendar. The most common reason for postponing the exam is not the difficulty of the material but lack of time. If study days are not blocked in the sprint plan, current work will eat them. That is why, in the budget above, working time is a separate — and the largest — item.
Exams in small groups, close to the training. It works best when the exam takes place within two or three weeks of the training. A longer gap reduces effectiveness, and certifying the whole team at once makes it hard to keep project work moving. Groups of two or three people in consecutive quarters work better.
How do you plan a QA team certification programme step by step?
A certification programme that supports the team’s goals starts with the goal, not with a list of exams. The roadmap below summarises how to approach it:
| Stage | Action | Control question | Outcome |
|---|---|---|---|
| 1. Goal | Define why you are certifying: tender, audit, shared language, role development | What changes if 100% of the team is certified? | One or two measurable goals |
| 2. Inventory | List existing certificates with syllabus versions | Who already has CTFL, and which version? | A team competence map |
| 3. Diagnosis | An anonymous sample exam for the whole team | Which chapters show gaps? | A list of development areas |
| 4. Matching paths | Assign a certificate to each role (table above) | Will this person use the knowledge within 6 months? | An individual plan |
| 5. Budget | Count cost including working time, not just fees | Does the team have 5–8 days per person without hurting projects? | A realistic budget, not an “invoice” budget |
| 6. Schedule | Spread exams across quarters, do not certify everyone at once | Who covers for people in training? | A plan without testing downtime |
| 7. Knowledge transfer | Certified people run internal sessions | Does the knowledge reach the team, or stay in the certificate? | Development of the whole team |
| 8. Measurement | After 6–12 months, check whether the goal from stage 1 was met | Have production defects, onboarding time or tender results changed? | A decision on the next stage |
The key takeaways:
- ISTQB today has four levels and three streams, and the most important syllabi — Foundation 4.0, Advanced Test Analyst 4.0, Technical Test Analyst 4.0 — are freshly updated. Certificates are valid for life, except at the Expert level.
- The exam is a small part of the cost. For a team of eight, 64% of the cost of certification is working time. A budget based on invoices alone understates the cost almost threefold.
- The payback threshold is low, but not zero. In our example, certification pays back if it saves each person about 3 working days a year for three years — or if it opens access to contracts that require certificates.
- A certificate confirms knowledge, not skill. It does not replace a practical task in recruitment or an assessment of project work.
- You do not have to certify everyone. Free ISTQB syllabi and the glossary give a team most of the value without exam fees.
At ARDURA Consulting we have been delivering software testing projects and building QA teams for clients in Poland, Europe, the Middle East and the USA for more than ten years. We work with testers certified at different ISTQB levels, but we select them primarily for practical skills and knowledge of the client’s domain. If you need a testing team that meets tender requirements or want to assess the maturity of your company’s test process, talk to our team.