Utilize Custom Fields for Effective Entity Tagging and Impact based testing

ACCELQ offers the flexibility to create custom fields at the Project level and assign them to key entities: Action, Context, Scenario, Test Case, and Test Suite. These custom fields enable efficient tagging of entities, providing ease of management and facilitating seamless test suite creation.

Below are the benefits and guidelines for utilizing custom fields effectively:

Benefits of Custom Fields

• Tailored Entity Tagging: Custom fields allow you to add specific attributes relevant to your testing process, such as Priority, Module, Test Type, Complexity, etc. This personalized tagging enhances the traceability and categorization of entities based on various criteria important for your testing process.
• Enhanced Filtering and Reporting: By using custom fields, you can filter and group entities based on their attributes, enabling better organization and quick access to relevant information during test design, execution, and analysis.
• Consistent Test Suite Creation: Leveraging custom fields when creating Test Suites ensures matching criteria for Scenarios and Test Cases, resulting in logically grouped and coherent test suites for executing against specific testing requirements.

Selecting Custom Fields

• To begin, assess the specific attributes that align with your testing requirements. Identify attributes that provide valuable insights into your testing process and align with your team's workflows.
• Common examples of custom fields include Priority, Module, Test Type, Owner Tester, Complexity, and more.
• Access the Project settings to create custom fields and assign them to the appropriate entities. Define the field name, data type, and applicable entities for each custom field.
• Ensure that the custom field names and attributes are intuitive, easy to understand, and relevant to your testing process.

Note about Scenario vs. Test Case Custom Fields

When assigning a custom field to the Scenario or test case, carefully consider the following distinction:

1. Scenario-Level: Assign custom fields at the Scenario level when the attribute applies uniformly to all Test Cases within that Scenario. For example, "Priority" reflects the overall business process priority.
2. Test Case-Level: Use Test Case-level custom fields for attributes that vary across individual Test Cases within the same Scenario. For instance, "Test Type" (sanity, smoke, regression) may differ for each Test Case.

Here are some examples: