Folders and organisation
The library is a folder tree. Folders nest as deeply as you like, and a test case belongs to exactly one — which is also how it belongs to a project, since the folder carries that.
Working with the tree
The left pane of Test Cases is the tree; the right is whatever the selected folder holds. Selecting All test cases lifts the folder filter and shows the project's whole library.
Folders can be created, renamed, moved and deleted from the tree's context menu. Deleting one cascades: its subfolders, their test cases and those cases' steps all go with it, and there is no undo. Only owners and admins can delete.
Folders as a menu
If you would rather give the list the whole width, Show directories as a menu — the last button in the tree's header — folds the tree away. Folders then open from a button beside the folder's name: the same searchable menu a phone shows, listing every folder and the test cases in it. Pick one to open it, or New directory at the bottom to add one. The button beside the menu brings the tree back.
The menu is for finding things. Renaming, colouring, moving and deleting folders, and dragging test cases between them, happen in the tree.
Which of the two you see is a per-person setting: it follows your account to any computer, and the same switch is on Settings → Behaviour. A phone always shows the menu, whichever you chose.
Colours
A folder can be given a colour, which is carried into the lists and pickers that mention it. This is the cheapest way to make a large library scannable — one colour per area, and the eye does the filtering.
Insights
Insights opens a panel beside the table with everything the list can be counted by. Every section follows the filters and the search, so it describes exactly what is on screen — narrow the table and the numbers narrow with it.
| Section | What it answers |
|---|---|
| In this view | How many cases, and how they split by state |
| Automation status | How much of this already runs on its own |
| Test creation trend | How fast this part of the library is growing, over a range you pick |
| Estimated run time | Roughly how long these take to run by hand — the midpoint of each estimate, added up |
| Linked to a requirement | How much of this proves something somebody asked for |
| Last updated | How stale it is: past week, past month, past 3 months, older |
| Top tags | Which labels cover the most ground — useful before building a hunt from a tag |
The pin keeps it open on every visit. It is a per-person setting, not a per-device one, and the same switch is on Settings → Behaviour.
Following a folder
Click Watch folder to be emailed when test cases are added to it.
A subscription covers the whole subtree: following Checkout also catches
Checkout / Payments. Deleting a folder cleans up the subscriptions pointing at
anything inside it, in both directions — somebody following
Checkout / Payments loses what they followed when Checkout goes.
Importing and exporting a folder
Next to Watch folder are Export and Import. Export takes the selected folder and everything under it, or the whole project when All test cases is selected; import offers that folder as its destination and lets you pick another. An import never changes or removes what is already there. See Importing and exporting.
Filtering rather than foldering
Folders are one axis. Before building a deep tree, consider whether tags do the job better: a case can carry many tags but only one folder, and a bug hunt can pull in every case carrying a given tag. Deep trees are hard to move through; a flat tree with good tags usually is not.
Every list screen also carries the same toolbar: a search box, a filter menu whose selections go into the URL, and a reset. A filtered list can be linked to and shared, because the filter is in the address.