Custom step fields
A test case step comes with an action, an expected result, additional data and screenshots. Custom step fields let your organization add its own columns to that — a Test data column, a Severity column, an Environment column, whatever the team actually needs.
:::info Plan Custom fields are available from the Standard plan upwards. :::
Adding one
Administration → Custom fields. Give the field a name and a type. It then appears on every step editor and every step reader in the organization.
Fields carrying rich text accept the same attachments as the rest of the app: screenshots, video, PDFs, logs. They render with the words first and the files underneath as a thumbnail strip, the same as pre-requisites do.
Where they show up
- In the step editor, as an extra field
- On the test case, in the expanded view of a step
- In a bug hunt execution, so the tester sees what you added
Removing one
Removing a field stops it being collected and stops it being shown. Consider carefully: a field that forty cases have filled in is forty pieces of writing that stop being visible.
Designing them well
The temptation is to add a field for everything. Two questions worth asking:
- Would a reader act on it? A field nobody reads is a field everybody has to fill in.
- Is it per-step or per-case? Custom fields are per step. Something true of the whole case — an environment, a persona — usually belongs in pre-requisites or a tag instead, where it is written once rather than eight times.