Inline Editing & Bulk Test Case Changes

AXQA allows common Test Case metadata to be changed directly from the Test Case Manager without opening each Test Case individually.
For larger updates, multiple Test Cases can be selected and updated together using Bulk Changes.

Why it matters

• Reduces repetitive Test Case editing.
• Makes release preparation and assignment changes faster.
• Allows large Test Case sets to be reorganized efficiently.

When to use it

• When assigning multiple Test Cases to another tester.
• When changing Priority or Category across a testing scope.
• When moving Test Cases between Groups.
• When changing Build or Execution Source for multiple Test Cases.

Core concepts

• Inline Editing – Editing one supported Test Case field directly in the table.
• Bulk Selection – Selecting multiple Test Case rows.
• Bulk Change – Applying the same new value to multiple selected Test Cases.
• Apply – Stages the selected bulk change.
• Save Changes – Persists staged bulk changes.
• Bulk Delete – Permanently deletes the selected Test Cases.

How it works

1. Select or edit Test Cases directly from the table.
2. AXQA validates the selected value.
3. Inline changes can be saved directly.
4. Bulk Changes are applied to selected rows and then persisted.
5. Changes are recorded in Test Case Audit History.

How to use it

Step 1: Edit a field directly

Supported Test Case fields can be edited from the table.

Current inline-editable fields include:

• Assign To
• Category
• Execution Source
• Priority
• Group
• Build

The Environment column is derived from the selected Build and is not edited independently.

Step 2: Select multiple Test Cases

Use the row-selection controls to select the Test Cases you want to update.

Only select Test Cases that should receive the same change.

Step 3: Choose a Bulk Change field

The Bulk Changes panel supports fields including:

• Assign To
• Priority
• Category
• Execution Source
• Build
• Group

Step 4: Select the new value

Choose the value that should be applied to the selected Test Cases.

Example:

Step 5: Apply and save

Click Apply to stage the change for the selected rows.

Review the changes.

Click Save Changes to persist them.

Step 6: Bulk delete when required

Selected Test Cases can also be deleted using the Bulk Delete action.

Only use Bulk Delete when the Test Cases should be permanently removed.

Best practices

• Filter the table before performing large bulk updates.
• Review selected Test Cases before clicking Save Changes.
• Use Bulk Changes for metadata updates rather than repeatedly opening Test Cases.
• Confirm Build changes carefully before execution.
• Review Audit History when investigating unexpected metadata changes.

Common mistakes

❌ Selecting too many Test Cases without reviewing the filtered scope.
✔ Confirm the selected rows before applying the update.

❌ Changing Environment directly.
✔ Select the appropriate Build; Environment is derived from that Build.

❌ Applying a bulk change but forgetting to save it.
✔ Complete the operation using Save Changes.

❌ Using Bulk Delete for temporary cleanup.
✔ Delete only Test Cases that should be permanently removed.

Security & permissions

• Inline and bulk operations are restricted to Test Cases in the Current Project.
• AXQA validates Build selections against the Current Project.
• AXQA validates assignees against the users eligible for the Current Project.
• Supported metadata changes are recorded in Audit History.
• Bulk Delete is a destructive operation and should be used carefully.

Related documentation

• Test Case Manager Overview
• Advanced Test Case Search, Filters & Saved Presets
• Test Case Audit History
• Organizing Test Cases with Metadata