LeoSuccess is an AI assistant built directly into LeoCore. It sits within your screen and enables you to manage tests, plans, and workspace content through plain conversation, without navigating menus or filling in forms manually.
You describe what you need in natural language and LeoSuccess takes action inside your workspace. It acts as an agent to carry out tasks, rather than just answering questions.
LeoSuccess is only available with certain packages.
Where to find LeoSuccess
You can find LeoSuccess across LeoCore in the main navigation.
When you open LeoSuccess, a chat opens with context depending on where you are in LeoCore.
What permissions LeoSuccess has
LeoSuccess can take actions with the same permissions you have. So, for example, if you have the Observer role in a workspace, you can use LeoSuccess to search and analyze, but not to create or refactor (you don’t have permission to create or edit).
To see your role and manage what roles others have, see more on managing team members.
What LeoSuccess can do
Bear in mind that LeoSuccess is under active development, with new features being added every week. LeoSuccess has the most capabilities in these areas:
Tests
Search for tests
Search for specific tests or tests that meet certain criteria (the platform they test, labels, last updated, or other). You can search by meaning, not only exact text.
Examples:
Find exploratory tests for the iOS platform
Show me all tests tagged as Payments
What tests do we have that deal with logging in?
What tests were updated in the past week?
Analyze tests
Analyze individual tests and test coverage across your test suite. Identify unclear or incomplete steps and where you have gaps in your test coverage.
You can also request all feedback from testers on test steps within a test to help you understand where additional clarity might be needed.
Examples:
Are the steps in this test clear enough? Should any of them be split into multiple steps?
Which features have the fewest tests?
Give me a coverage summary of the login feature
Summarize the step feedback on this test and suggest what to fix
Refactor tests
If you find any tests that could use improvements, direct LeoSuccess to make changes to them. You can offer specific instructions you want to be carried out or general requests for improvement.
Examples:
Mark this test as high priority
Refactor this test – the steps are too vague
Improve the expected results for the login test
Clean up this test to match the exploratory test guidelines
Create tests
Create tests that automatically fit the Testlio guidelines for optimizing test clarity and coverage. You can focus on one test at a time, or create multiple tests at once from a single prompt.
Examples:
Create a test for the login flow with invalid credentials
Add a test for checkout with an expired payment card and mark it as high priority
Import tests
If you have many tests you want to add to your test suite, get LeoSuccess to help you upload them all in a single file and mapping the columns to the fields in LeoCore.
To upload a file, click + (Attach options) > Upload file.
Once you have uploaded a file, LeoSuccess maps its columns to LeoCore fields and shows you a preview. After confirmation, it creates the tests.
Take action on tests
Archive tests you no longer need. Archiving a test is the same as deleting it.
Examples:
Archive TEST-124
Archive TEST-11, TEST-12, and TEST-13
Archive all the tests tagged with the old Checkout v1 feature we retired
Plans
Search for plans
Search for specific plans and see which tests a plan includes.
Examples:
Find me a test plan that covers the checkout process
Show me all plans that include a test on adding a credit card
Analyze plans
Analyze individual plans and see where coverage might need to be expanded. Look across your test suite for plans that meet certain criteria.
Examples:
Is there anything about this plan that could be improved?
What test plans do we have for the mobile app?
Refactor plans
If you find any plans that could use improvements, direct LeoSuccess to make changes to them. You can offer specific instructions you want to be carried out or general requests for improvement.
Examples:
Add all Authentication tests to the regression plan
Reorder the tests in this plan by priority
Add a description to the plan that covers the included tests
Create plans
Create plans to expand your coverage, either one at a time or multiple plans from a single prompt.
Examples:
Create a test plan for the Q3 regression cycle
Build a plan for payments testing with existing high-priority tests
Issues
Search for issues
Use LeoSuccess to search for specific issues or issues that meet certain criteria (the feature they come from, the labels they have, or other).
Examples:
Show me all open high-severity issues about the Payments feature
List all issues with the needs-triage label
Analyze issues
Analyze trends in your issues to see what it might mean for your priorities going forward. Find patterns or gaps that might guide what actions you need to take.
Examples:
What are the most common severity levels reported this month?
Summarize issue trends in Payments over the last quarter
Refactor issues
If you find any issues that could use improvements, direct LeoSuccess to make changes to them. You can offer specific instructions you want to be carried out or general requests for improvement.
Examples:
Rewrite this issue description so it's clearer and includes reproduction steps
Clean up the description for issue 204 so it's easier to scan
Add labels to this issue just like with issue 12345
Create issues
Create issues from a plain description. LeoSuccess shows you the issue and asks before creating it. LeoSuccess asks any questions necessary to get a clear issue.
Examples:
Log a new high-severity bug: checkout button unresponsive on iOS Safari
Create an issue for the broken CSV export, tagged with Reporting
Take action on issues
Issues have a specific workflow with different statuses. Move issues through the workflow or take other common actions.
Examples:
Approve all triaged issues about the Payments feature
This issue is fixed – close it for me
Known current limitations
LeoSuccess is under active development and so does not cover every need at the moment. The following list includes areas without features at the moment where work is being done:
Doesn’t know current execution. LeoSuccess can’t get context from runs and reports and so can’t tell you information such as what tests are failing.
Doesn’t know workspace-specific guidelines. Each workspace can contain specific guidelines such as issue templates to shape how issues and tests are created. These are not currently available to LeoSuccess.
Test import only supports CSV and XLSX files.
Context is added only at the start of a chat. If you navigate to a different section of LeoCore, you don’t get new context automatically. You can add different context by clicking + (Attach options) > Add current view as context.
Can’t archive or comment on issues.
If you run into any issues outside this list, please reach out to your Engagement Manager to let them know.