Skip to content

ZeuZ Best Usage Review Template

Sakib75 edited this page Oct 31, 2024 · 1 revision

ZeuZ Best Practices Guide

1. Testcase

Check Status Description Status
Folder should be selected correctly Ensure the correct folder is chosen for organizing test cases. -
Feature should be selected correctly Verify that the correct feature is selected for better classification. -
Labels should be added Apply relevant labels to improve filtering and categorization. -
Steps should have proper descriptions and expected outcomes Each step should include clear instructions and expected results for better readability. -
Maximize the usage of Global Steps Reuse global steps wherever possible to improve consistency and maintainability. -
Make use of Variable declaration in local steps Declare variables locally to enhance test flexibility and readability. -
Actions should be named Give actions meaningful names for clarity and better traceability. -
Revert to the original state for rerun readiness If the test case creates or modifies anything, ensure it reverts to its original state. -

2. Uniform Testcase naming convention

All test cases should follow a consistent naming convention. For example: Category > Edit Category > Edit and validate the category

Comment

3. Folder structure

The naming convention should align with project requirements and can be organized by factors like operating system, testing phase, or other relevant criteria.

Comment

4. Features structure

This structure should correspond to different product features. Sub-features should be nested within main features, allowing the structure to expand recursively as needed.

Comment

5. Deploy Settings

Use presets

Comment

6. Test Plan

Comment

7. Test SET

The SET names should be well defined

Comment

8. Presets

Comment

9. Scheduler

Comment

10. DataStore

Comment

11. Version

It should correspond to the development cycle and follow a consistent naming convention. If the product doesn’t adhere to a specific development cycle, we should establish a system that supports efficient review of our testing cycle.

Comment

12. Milestone

It should correspond to the development cycle and follow a consistent naming convention. If the product doesn’t adhere to a specific development cycle, we should establish a system that supports efficient review of our testing cycle.

Comment

13. Label

This acts like a tag or label for a test case, making it easier to filter test cases by specific categories or genres.

Comment