Příklad šablony testovacího plánu

What is a Test Plan Template?

A Šablona zkušebního plánu is a detailed document describing the test strategy, objectives, schedule, estimation, deliverables, and resources required for testing. It helps determine the effort needed to validate quality and serves as a blueprint controlled by the Test Manager.

Vytvoření Testovací plán is mandatory to ensure success of your testing project. If you are new to it, refer to Jak vytvořit testovací plán.

Stáhněte si vzorovou šablonu testovacího plánu

Test Plan Template Structure

Below are the important constituents of a Test Plan template, explained in order:

• 1. Úvod
• 1.1 Rozsah
• 1.1.1 V rozsahu
• 1.1.2 Mimo rozsah
• 1.2 Cíl kvality
• 1.3 Role a odpovědnosti
• 2. Metodika testování
• 2.1 Přehled
• 2.2 Úrovně testu
• 2.3 Třídění chyb
• 2.4 Kritéria pozastavení a požadavky na obnovení provozu
• 2.5 Úplnost testu
• 3. Test Deliverables
• 4. Resource & Environment Needs
• 4.1 Testovací nástroje
• 4.2 Testovací prostředí
• 5. Terms/Acronyms

1) Úvod

The Introduction provides a brief overview of the test strategies, processes, workflow, and methodologies used for the project.

1.1) Rozsah

---

Scope is split into two parts so that the testing boundary remains unambiguous.

1.1.1) V rozsahu

In Scope defines the features, functional, or non-functional requirements of the software that bude testováno.

1.1.2) Mimo rozsah

Out of Scope defines the features, functional, or non-functional requirements of the software that nebude testováno.

1.2) Cíl kvality

---

Here you mention the overall objectives that the team plans to achieve through manual testing and automation testing. Some objectives of a typical testing project include:

• Ensure the Application Under Test (AUT) conforms to functional and non-functional requirements.
• Ensure the AUT meets the quality specifications defined by the client.
• Identify and fix bugs before the application goes live.

1.3) Role a odpovědnosti

---

Provide a detailed description of the roles and responsibilities of the different team members involved, such as:

• QA analytik
• Správce testů
• Správce konfigurace
• Vývojáři
• Instalační tým

Mezi ostatními.

👉 Zaregistrujte se do projektu bezplatného živého testování softwaru

2) Metodika testování

This section determines the lifecycle, levels, and rules used to govern test execution.

2.1) Přehled

---

Mention the reason for adopting a particular test methodology for the project. The test methodology selected for the project could be:

• Vodopád
• Iterativní
• Agilní
• Extrémní programování

The methodology selected depends on multiple factors. You can read more about test methodology zde.

2.2) Úrovně testu

---

Test Levels define the types of testing to be executed on the Application Under Test (AUT). The chosen levels primarily depend on the scope of the project, time, and budget constraints.

2.3) Třídění chyb

---

The goal of bug triage is to:

• Define the type of resolution for each bug.
• Prioritize bugs and determine a schedule for all “To Be Fixed” bugs.

2.4) Kritéria pozastavení a požadavky na obnovení provozu

---

Suspension criteria define the conditions under which all or part of the testing procedure will be paused. Resumption criteria determine when testing can resume after it has been suspended.

2.5) Úplnost testu

---

Here you define the criteria that will deem your testing complete. For instance, common criteria to check test completeness would be:

• 100% test coverage achieved.
• All manual and automated test cases executed.
• All open bugs are fixed or planned for the next release.

3) Test výstupů

List every artifact produced across the testing lifecycle. Recording them in advance prevents missed handovers between teams.

4) Potřeby zdrojů a prostředí

List tools and infrastructure to secure budgets, licenses, and environments before execution begins.

4.1) Testovací nástroje

---

Make a list of tools such as:

• Nástroj pro sledování požadavků
• Nástroj pro sledování chyb
• Nástroje automatizace

These are required to test the project effectively.

4.2) Testovací prostředí

---

Mention the minimum technické vybavení requirements that will be used to test the application.

Následující software is required in addition to client-specific software:

• Windows 11 a výše
• Microsoft 365 (or Office 2021 and above)
• MS Exchange atd.

5) Termíny/zkratky

Document any terms or acronyms used in the project so newcomers can read the plan without ambiguity.

Stáhněte si výše uvedený formát šablony testovacího plánu

Sample Test Plan Document: Banking Web Application Example

The following worked example shows how the template above is filled in for the Guru99 Bank web application.

1. Úvod

The Test Plan prescribes the scope, approach, resources, and schedule of all testing activities for the Guru99 Bank project. It identifies the items and features to be tested, the types of testing performed, the personnel responsible, and the risks associated with the plan.

1.1 Rozsah

1.1.1 V rozsahu

All features of the Guru99 Bank website defined in the software requirement brejle need to be tested.

Název modulu	Použitelné role	Description
Dotaz na zůstatek	Manager, Customer	Zákazník: A customer can have multiple bank accounts and can view balances of his accounts only. Manažer: A manager can view the balance of all customers under his supervision.
Převod prostředků	Manager, Customer	Zákazník: A customer can transfer funds from his own account to any destination account. Manažer: A manager can transfer funds from any source account to any destination account.
Mini prohlášení	Manager, Customer	A mini statement shows the last 5 transactions of an account. Zákazník: Sees the mini-statement of his own accounts only. Manažer: Sees the mini-statement of any account.
Přizpůsobené prohlášení	Manager, Customer	A customized statement filters and displays transactions in an account by date or transaction value. Zákazník: His own accounts only. Manažer: Any account.
Změnit heslo	Manager, Customer	Zákazník: Can change the password of his own account. Manažer: Can change the password of his own account but not those of his customers.
Nový zákazník	Manažer	Manažer: Manažer může přidat nového zákazníka.
Upravit zákazníka	Manažer	Manažer: Can edit details such as address, email, and telephone of a customer.
Nový účet	Manažer	The system provides 2 account types: Saving and Current. A customer can hold multiple saving accounts (sole or joint) and multiple current accounts. Manažer: Can add a new account for an existing customer.
Upravit účet	Manažer	Manažer: Can edit account details for an existing account.
Smazat účet	Manažer	Manažer: Can delete an account belonging to a customer.
Smazat zákazníka	Manažer	A customer can be deleted only if she has no active current or saving accounts. Manažer: Can delete a customer.
Vklad	Manažer	Manažer: Can deposit money into any account, typically when cash is deposited at a bank branch.
Výběr peněz	Manažer	Manažer: Can withdraw money from any account, typically when cash is withdrawn at a bank branch.

1.1.2 Mimo rozsah

These features are not tested because they are not part of the software requirement specs:

• Uživatelská rozhraní
• Hardwarová rozhraní
• Softwarová rozhraní
• Database logical design
• Komunikační rozhraní
• Zabezpečení a výkon webových stránek

1.2 Cíl kvality

Cílem testu je ověřit si the functionality of the Guru99 Bank website. The project should focus on testing the bankovní operace, such as Account Management, Withdrawal, and Balance enquiry, to záruka that all these operations work Normálně in a real business environment.

1.3 Role a odpovědnosti

Projekt by měl využít outsourcováno members as testers to save on project cost.

Ne.	Člen	Úkoly
1.	Správce testů	Manages the entire project, defines project direction, and acquires appropriate resources.
2.	Tester	Identifies and describes appropriate test techniques, tools, and automation architecture; verifies the test approach; executes tests; logs results; reports defects. Outsourced members.
3.	Vývojář v testu	Implements test cases, test programs, test suites, etc.
4.	Správce testu	Builds and maintains the test environment and assets; supports testers during execution.
5.	Členové SQA	Take charge of quality assurance and confirm whether the testing process meets the specified requirements.

2. Metodika testování

2.1 Přehled

The Guru99 Bank project follows an Agile-friendly testing methodology, allowing testers to align with rapid development sprints while maintaining structured documentation.

2.2 Úrovně testu

In the Guru99 Bank project, three types of testing should be conducted:

• Testování integrace: Individual software modules are combined and tested as a group.
• Testování systému: Conducted on a complete, integrated system to evaluate compliance with specified requirements.
• Testování API: Tests every API exposed by the software under test.

2.3 Třídění chyb

Bug triage meetings are held twice a week to classify defect severity, owner, and target fix release.

2.4 Kritéria pozastavení a požadavky na obnovení provozu

If 40% of test cases have neúspěšný, suspend testing until the development team fixes all failed cases.

2.5 Úplnost testu

• Určuje kritéria, která označují a úspěšný completion of a test phase.
• Běžecké tempo is mandatory at 100% pokud není uveden jasný důvod.
• Míra průchodu is 80%; achieving the pass rate is povinné.

2.6 Project Tasks, Estimation, and Schedule

Úkol	Členové	Odhadované úsilí
Vytvořte specifikaci testu	Testovací návrhář	170 člověkohodin
Proveďte provedení testu	Tester, správce testu	80 člověkohodin
Zkušební protokol	Tester	10 člověkohodin
Zkušební doručení	Správce testů	20 člověkohodin
Celková cena	-	280 člověkohodin

Program: The team commits to completing these tasks across the agreed test cycle window.

3. Test Deliverables

Test deliverables for the Guru99 Bank project are organized into three phases.

Before the testing phase:

• Test plan document.
• Testovací případy dokumenty.
• Test design specifications.

During the testing phase:

• Test tool simulators.
• Testovací data.
• Test traceability matrix, error logs, and execution logs.

After the testing cycles are over:

• Test results and reports.
• Hlášení závady.
• Installation and test procedure guidelines.
• Release notes.

4. Resource & Environment Needs

4.1 Testovací nástroje

Ne.	Výzkumné	Description
1.	Server	A database server running MySQL and a web server running Apache.
2.	Testovací nástroj	A tool that can auto-generate test results into a predefined form and automate test execution.
3.	Síť	A LAN gigabit setup and one internet line with a minimum speed of 5 Mb/s.
4.	Počítač	At least 4 workstations running Windows 11, with 8 GB RAM and a 3.4 GHz CPU.

4.2 Testovací prostředí

This subsection lists the minimum hardware and software requirements used to test the application. The following software is required in addition to client-specific software:

• Windows 11 a výše
• Microsoft 365 (or Office 2021 and above)
• MS Exchange atd.

How AI Helps in Test Planning

Modern test planning increasingly uses AI to compress effort and surface blind spots. Generative assistants such as ChatGPT, Claude, or Gemini can draft an initial Test Plan from a requirements document, suggest missing edge cases, and produce traceability matrices automatically. Machine learning models flag risky modules from historical defect data, helping the Test Manager focus effort where it matters most.

However, AI assistance does not replace human judgment. Reviewers must validate scope, regulatory coverage, and business intent before approving any AI-generated plan. Treat AI suggestions as a first draft, not the final document.

Best Practices for an Effective Test Plan

A well-written test plan keeps every stakeholder aligned. Apply these best practices when authoring your document:

• Udržujte to stručné: Use clear language and bullet lists; avoid jargon that slows non-QA readers.
• Udělej to Reviewable: Share early with developers and Business Analysts to catch missing requirements.
• Quantify Exit Criteria: Define numeric coverage, pass rate, and defect thresholds.
• Tie Risks to Mitigations: Pair every risk with a containment or fallback strategy.
• Version-Control the Plan: Store it in a documentation tool to track changes across the project.

Nejčastější dotazy