Test Case Comments & To-Dos in AXQA | QA Collaboration

Test Case Comments & To-Dos

AXQA provides Comments and To-Dos directly inside individual Test Cases to support collaboration without separating operational notes from the testing context.
Comments preserve discussion, while To-Dos track smaller actions that still need to be completed.

Why it matters

Keeps QA discussion connected to the relevant Test Case.
Helps testers track small follow-up actions.
Reduces the need to manage simple Test Case notes in separate systems.

When to use it

When another tester needs additional context.
When a Test Case requires a small follow-up action.
When documenting a clarification or testing observation.
When preparing unfinished work for another team member.

Core concepts

Comment – A text note attached to the Test Case.
To-Do – A small action item attached to the Test Case.
Done – Indicates that a To-Do has been completed.
Current Project – The active project context required to access the Test Case.

How it works

Open an existing Test Case.
Use the Comments or To-Do section.
Comments are stored with the Test Case, user, project, and creation time.
To-Dos can be added, completed, reopened, or deleted.
The information remains connected to the Test Case.

How to use it

Step 1: Add a Comment

Open the Comments tab.

Enter the information you want to share and click Add Comment.

The comment is displayed with information about the user and creation time.

Step 2: Use Comments for context

Useful comments may include:

Testing clarification
Environment observations
Reproduction information
Coordination notes
Follow-up information

Avoid placing passwords, tokens, API keys, or other secrets in Comments.

Step 3: Add a To-Do

Open the To-Do tab.

Enter the action that still needs to be completed.

Example:

Retest login flow after API deployment.

Step 4: Complete or reopen a To-Do

Use the To-Do status control to mark an item as completed.

A completed To-Do can be toggled again when additional work is required.

Step 5: Delete a To-Do

Delete To-Dos that are no longer relevant.

This removes the To-Do from the Test Case.

Best practices

Use Comments for information and discussion.
Use To-Dos for actionable follow-up work.
Keep To-Dos short and specific.
Do not store sensitive credentials in either feature.
Close or delete obsolete To-Dos to keep the Test Case clean.

Common mistakes

❌ Using Comments as a password or credential store.
✔ Keep sensitive information in the appropriate protected configuration fields.

❌ Creating vague To-Dos such as "check later."
✔ Describe the exact follow-up action required.

❌ Leaving completed To-Dos active indefinitely.
✔ Mark them complete when the work is finished.

Security & permissions

Comments and To-Dos are tied to the Test Case and its project.
The Current Project must match the Test Case project.
Project permission checks apply to To-Do operations.
User input is validated and sanitized before supported operations are stored or displayed.
Sensitive authentication information should never be placed in Comments or To-Dos.

AXQA

Did You Know?