In the context of the Testlio Platform, a test plan refers to a collection of test cases that are run. Think of it as a container holding all the test cases.

Creating a test plan on the Testlio Platform involves the following steps:

There are two types of test plans:

In the Testlio Platform, all new test plans should use the Functional test service.

Following a few principles helps ensure that your test plans are logically structured, focused, clear to testers, and reviewed for any issues or inconsistencies before execution, leading to effective and efficient testing processes.

Test plans should contain a logical grouping of functions or flows that need to be verified from both the end-user and coordinator perspective. Ideally, create one plan for each feature or specific functionality to maintain clarity and focus.

Testers only have access to the specific plan they are assigned to, without seeing the larger picture. Any information needed to understand the test cases should be embedded within the test cases themselves so testers have all they require to execute the assigned plan.

Keep exploratory test cases and scripted test cases in different test plans. This allows testers to have a clear focus and mindset for each type of testing. Mixing scripted and exploratory tests within a plan often leads to suboptimal results. Additionally, targeting different testers for each type of testing can lead to better outcomes.

After editing a test plan, use the preview feature to review the entire plan. This helps you catch potential inconsistencies and problems before the plan is executed, ensuring quality and accuracy.

Ordering tests in static plans in a logical and efficient manner leads to a smooth testing flow, optimized coverage, and timely identification of critical issues. This section presents some tips for good ordering.

If you need to provide additional context or information to testers about the engagement, workspace, or product, consider starting the plan with an "Instructions Test". This test includes details such as specific accounts to be used and relevant guides/voiceovers to provide the necessary context. This is optional and can be helpful when documentation is otherwise missing or run instructions are inconvenient.

Order the tests in a logical manner within the plan. If a plan includes simple and complex features, start with the more simple ones. Allow testers to progress through the app naturally, considering their feature knowledge and complexity.

Be mindful of the particular run’s focus. Critical functionality such as new features, impacted areas, or critical business flows should be covered earlier in the run. This means potential showstoppers can be identified earlier in the testing process.

While test cases should be independent, you can often optimize for data generation and prerequisites through test sequencing. For example, if a test case requires using a newly created account and there's a separate test for account creation, put the account creation test first.