✳ IskraAI

Test Plan: How to Combine Manual Work and AI

Testing is not only about finding bugs, but also planning scenarios that can break the system. Manual test plan creation takes time, and the AI tool 'Test Plan' helps quickly generate a draft with successful, failed and boundary cases. However, blindly trusting the machine is not advisable: it is important to understand where automation ends and your responsibility begins. In this article we will see how to effectively combine manual work and AI using a password reset form as an example.

Abrir ferramenta: Construtor de plano de teste ↗

What the 'Test Plan' tool can do

'Test Plan' is a web tool that, based on your textual task description, generates a structured test plan. You enter an idea or functionality in the 'Your text or idea' field, specify the platform or application in the 'Platform or application' field and click 'Generate'. You get plain text with a set of test cases: successful scenarios, failed and boundary conditions. The result can be copied or downloaded as TXT.

The tool does not require registration, does not automatically save data and does not integrate with other systems. It works only with text: does not support document upload, OCR, DOCX or PDF export, batch processing. This is important to consider when planning: if you need a test plan for a complex system with many integrations, you will have to manually supplement the result.

Input limits: first field up to 8000 characters, second up to 1000. The model can make mistakes, and queue and service availability vary. Therefore, the tool should be perceived as an assistant for generating ideas, not as a replacement for an analyst or tester.

Example input: 'Password reset form that sends a one-time link to email'. Platform: 'Web application'. Result: a list of tests including successful reset, invalid email, expired link, link reuse.

Which parts of the task to assign to AI

AI is good at routine enumeration of options. It can be assigned to generate typical successful scenarios: for a password reset form this would be entering a correct email, following the link, setting a new password. The tool will also propose failed cases: non-existent email, empty field, wrong format, password mismatch. Boundary conditions - password length, special characters, resending the letter - also often end up in the draft.

Delegate AI the initial structuring: breaking down into categories, formulating steps, expected result. This saves time at the brainstorming stage. But do not ask the tool to set priorities or assess risks - for this you need project context, which you know better.

If you have a checklist or requirements, you can insert them into the input field so AI takes them into account. For example, indicate that the link is valid for 15 minutes and the password must contain at least 8 characters. Then generated cases will be more accurate.

Input: 'Password reset: email, link valid for 15 minutes, password from 8 characters, must contain a digit and a letter'. AI will add checks for link expiry and password complexity.

What to check yourself

After generation, be sure to check that all key scenarios are covered. AI may miss product-specific cases: for example, password reset for a user who is already logged in, or behavior when the account is blocked. Also check that there are no duplicate or unrealistic tests.

Manually evaluate boundary values. The tool may suggest a password of 7 characters, but if the requirement is minimum 8, this is not a boundary, but a failure. Make sure boundaries match your documentation. Check that negative scenarios with unexpected data are covered: emojis, spaces, SQL injections.

Manually set priorities: which tests are critical for the release, which can be postponed. AI does not know your deadlines and risks. Also check step formulations - they must be unambiguous so any tester can reproduce the scenario.

AI suggested test 'entering a 7-character password'. You check the requirements: minimum 8, so this is a failed case, not a boundary. Fix it.

When the service is not suitable

The tool will not suit if you need a test plan for a system with many integrations, where important are API call sequences, database work, message queues. AI does not see the architecture and cannot propose comprehensive scenarios. In such cases it is better to use specialized tools or manual design.

Also do not rely on the service if high accuracy and security are required. For example, testing financial transactions or medical data: errors in the test plan can lead to missing critical bugs. Here an experienced tester and a strict process are needed.

If you already have a detailed test plan, AI will not give a significant gain. It is useful at early stages when you need to quickly jot down ideas. For regression testing or complex scenarios it is better to use verified checklists.

For testing a bank transfer with balance checking, limits and blocks AI will not account for all business rules. Better to make a plan manually.

Practical example: password reset form

Consider a fictional example: a web application with a password reset form. The user enters an email, receives a one-time link letter, follows it and sets a new password. We want to create a test plan with AI.

We enter into the tool: 'Password reset form, sends a one-time link to email. Link valid for 15 minutes. Password from 8 characters, must contain a digit and a letter'. Platform: 'Web application'. We click 'Generate'.

The tool outputs a draft. Successful cases: correct email, follow link, enter valid password, successful reset. Failed cases: non-existent email, empty field, wrong email format, password mismatch, weak password. Boundary cases: email with spaces, link after 14 minutes 59 seconds, password exactly 8 characters, link reuse.

We check manually: we add a case when the user is already logged in and requests a reset; we check that the link is single-use; we verify that on resend the old link is invalidated. We also add a check for SQL injection in the email field. We set priorities: critical - successful reset and link expiry.

Final test plan: 1. Successful reset. 2. Invalid email. 3. Empty field. 4. Link expired. 5. 7-character password. 6. 8-character password with digit and letter. 7. Link reuse. 8. SQL injection.

How to check the result and limitations

After generation review each test case for compliance with requirements. Make sure steps are reproducible, expected result is unambiguous. Check that there are no tests that cannot be executed in your environment. For example, AI may suggest an email check, but you may not have access to the mailbox.

Remember the tool limitations: it does not save history, does not export to DOCX, does not support file upload. The model can make mistakes, and the generation queue may delay. Do not use the result without adapting it to your project.

The tool does not guarantee full coverage. It only helps to start. Always supplement the plan with your knowledge of the product, risks and business logic. Testing is a creative process, and AI is just an assistant here.

Check: if AI suggested test 'entering email without @', make sure your validation really should reject such an address. If yes - the test is correct.

The AI tool 'Test Plan' accelerates the creation of a test scenario draft, but does not replace analytics. Delegate to it the generation of typical cases, and manually check boundaries, priorities and specifics. Use the service at early stages when you need to quickly get ideas. Remember the limitations: text up to 8000 characters, no integrations, possible model errors. Combining automation and manual work will give you a quality test plan and save time.

Abrir ferramenta: Construtor de plano de teste ↗

As traduções da interface são assistidas por máquina e podem precisar de refinamento.