Start with a Mind Map
Explore scenarios visually, organize branches, then convert a Mind Map branch into a Test Group and its Section hierarchy. Carry the structure from planning into test management.
09 / Adapt
Built around the way your team works
Every team has its own testing habits. From Mind Maps or Sections to either direction of Test Case and Test Run sync, Armoury offers choices that fit the workflows most businesses already use.
Different habits. One Armoury.
Choose the path that fits your team
How you organize tests
Mind Map
Turn branches into test structure
or
Test Group + Section
Build the hierarchy directly
Where you update cases
Test RunTest Case
Refine during execution, then sync back
Test CaseTest Run
Update the library, then sync to existing runs
Your business should not have to adapt to a tool. Armoury gives your team room to keep the working habits that already make sense.
Your structureMind Maps or Sections
Either directionsync cases where needed
Familiar habitsa shorter path to getting started
More than one way forward
Keep the process that works for your team.
Some teams think visually; others build the hierarchy directly. Some refine cases while testing; others maintain the library first. Armoury supports each approach.
Build Sections directly
Create Sections and nested Sections inside a Test Group to express products, modules, or scenarios. Teams that prefer a hierarchy can organize coverage in the place they already manage cases.
Refine in a Test Run, then sync back
When execution reveals a case that needs improving, edit it in the Test Run and sync the changes back to the source Test Case. Let what the team learns during testing improve the reusable library.
Update Test Cases, then sync to runs
If your team maintains the library first, edit the source Test Case and sync the update to existing Test Runs as needed. Follow the review and maintenance order your team is used to.
A familiar start after migration
Bring your test knowledge. Keep your working rhythm.
Moving from another test management system is easier when the new tool supports familiar structures and editing habits. Start with what your team already knows.
Bring your existing cases
Import CSV or XLSX files, map the fields, and preview the content before importing the test knowledge your team has built.
Use a familiar structure
Organize Test Groups and Sections directly, or start new coverage from a Mind Map. Choose the approach that reflects how your team understands the product.
Keep your maintenance rhythm
Decide whether to refine in Test Runs or maintain Test Cases first, then sync where needed. Your team can get started quickly with a familiar way of working.
A tool that fits your business
Keep the habits. Move the work forward.
Armoury brings different ways of structuring, editing, and syncing tests into one system. Most teams can find a path that fits their existing process, so even a move from another test management tool feels familiar from the start.
Review plans and evaluation