Test Profile

The test profile holds the test's identity and organization metadata. None of it affects what candidates experience — it exists so that you and your teammates can find, group, and recognize tests as the library grows.

Profile Fields

• Title — the test's display name everywhere: the tests table, the task wizard, reports.
• Description — free text for teammates: purpose, target audience, version notes.
• Folder — the single place the test lives in your tests tree. Use folders for your primary structure (department, client, program).
• Labels — free-form markers a test can carry several of (“2026-intake”, “needs-review”). Use labels for cross-cutting states that don't fit the folder tree.
• Tags — key–value pairs (“level: advanced”, “language: de”) for structured filtering.
• Favorite — pins the test for quick access in your own view.

Rule of thumb: folder = where it belongs (one place), labels = what state it's in (many, transient), tags = what it is (structured facts). Teams that keep these three roles distinct keep large test libraries searchable.

Folder vs labels vs tags

Test ID

Every test has a permanent unique ID, shown in the profile. You'll use it when referencing the test in API calls and integrations, and when contacting support about a specific test — it identifies the test unambiguously regardless of renames.

Test tags are independent from question tags — tagging a test does not tag its questions, and question filters don't see test tags.

Good to know