Test Plan: Combining Manual Work and AI

What the 'Test Plan' Tool Can Do

'Test Plan' is a web tool that generates a structured testing plan based on your textual description of a task. 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 press 'Generate'. You receive plain text with a set of test cases: successful scenarios, failed cases, and boundary conditions. The result can be copied or downloaded as a TXT file.

The tool does not require registration, does not automatically save data, and does not integrate with other systems. It works only with text: it does not support document uploads, 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: the first field up to 8000 characters, the second up to 1000. The model may make errors, and queue and service availability vary. Therefore, the tool should be perceived as an assistant for generating ideas, not 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, reuse of link.

Which Parts of the Task to Delegate to AI

AI is good at routine enumeration of options. It can be entrusted with generating typical successful scenarios: for a password reset form, this includes entering a correct email, following the link, and setting a new password. The tool will also suggest failed cases: non-existent email, empty field, incorrect format, password mismatch. Boundary conditions — password length, special characters, resending the email — also often appear in the draft.

Delegate to AI the primary 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 that 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, specify 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 expiration and password complexity.

What to Check Yourself

After generation, necessarily check that all key scenarios are covered. AI may miss specific cases for your product: for example, password reset for a user who is already logged in, or behavior when the account is blocked. Also check for 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. Ensure boundaries correspond to your documentation. Check that negative scenarios with unexpected data are covered: emojis, spaces, SQL injection.

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

AI suggested a test 'entering a 7-character password'. You check the requirements: minimum 8, so this is a failed case, not a boundary. You correct 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 safety 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 draft 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 hypothetical example: a web application with a password reset form. A user enters an email, receives a letter with a one-time link, follows it and sets a new password. We want to make a test plan with the help of AI.

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

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

You check manually: add a case when the user is already logged in and requests reset; check that the link is single-use; clarify that upon resend the old link is invalidated. Also add a check for SQL injection in the email field. Set priorities: critical — successful reset and link expiration.

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. Reuse of link. 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's limitations: it does not save history, does not export to DOCX, does not support file uploads. The model may make errors, and the queue for generation may delay. Do not use the result without adaptation 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 merely an assistant here.

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