The Status List feature in ACCELQ provides a centralized and configurable approach to manage and track the lifecycle of various entities across your project, such as Test Suites, Scenarios, Contexts, Actions, and more. Project administrators can define custom status values, associate them with distinct colors, and categorize these statuses to enhance clarity, consistency, and visibility throughout testing and automation activities.
Key Capabilities:
-
Custom Status Definition: Define custom statuses tailored to your project's unique workflow.
-
Color Coding: Assign distinct colors to each status, providing immediate visual clarity.
-
Categorization: Organize statuses into categories (e.g., "To Do", "In Progress", "Done") to streamline workflow management.
Creating and Editing Status Items:
Project Administrators can configure the Status List from the Project Configuration screen.
-
Navigate: Go to the Project Configuration area.
-
Select "Status List": Choose the Status List option from the menu.
-
Add a Status:
-
Click the "+" button to add a new status.
-
Enter the Status Name.
-
Select a Color Code.
-
Choose a Category (To Do, In Progress, Done).
-
Click "Done" to save.
-
-
Edit Existing Status:
-
Locate the status you want to edit in the Status List.
-
Click the options icon (three dots) next to the status.
-
Modify the Status Name, Color Code, or Category as needed.
-
Click "Done" to apply your changes.
-
-
Delete a Status:
-
Click the options icon (three dots) next to the status.
-
Choose the delete option and confirm the deletion.
- Note: When deleting an existing Status, you are required to select a replacement-Status to update existing references.
-
Entities where Status can be applied:
-
You can apply the status value across all the major entities in ACCELQ:
- Test Suite (Manual and Automation)
- Scenario (Manual and Automation)
- Context
- Action
- When an entity is newly created, the first status in the "To Do" category is applied by default.
- You can reorder the Status labels simply by drag/drop in the Project Admin area.
Example Use Cases for Status Values in Testing:
-
New: Test elements recently created and yet to be worked upon.
-
Work in Progress: Actively undergoing development or refinement.
-
Under Review: Awaiting peer or QA review.
-
Completed: Fully developed, reviewed, and ready for execution.
-
On Hold: Temporarily paused activities, awaiting resolution of dependencies or clarifications.
-
Blocked: Unable to proceed due to external dependencies or identified blockers.
-
Deprecated: No longer in active use or replaced by updated scenarios/actions.
Best Practices:
-
Consistency: Standardize statuses across projects for clear understanding and reporting.
-
Minimalism: Limit the number of statuses to essential ones to avoid complexity.
-
Visibility: Use contrasting colors to ensure quick visual recognition of critical statuses.
-
Clear Definition: Clearly document each status definition and intended use within the project guidelines.
-
Regular Review: Periodically review and update the status list to reflect changing processes or project evolution.
By thoughtfully utilizing the Status List feature, teams can significantly enhance transparency, manage testing workflows efficiently, and improve communication within their testing processes.
Comments
0 comments
Article is closed for comments.