Shared Suite | Bondar Academy

Lesson Summary

Lesson Overview: This lesson discusses the concept of shared suites in testing environments, specifically how to manage multiple test suites for different environments using a feature called test trigger . Key Concepts: Shared Suites: Allows sharing of existing tests, test data, and information across different test suites. Test Environments: Different environments (e.g., QA, Staging) require separate configurations. Creating Test Suites: New test suites can be created for different environments without modifying the original suite. Steps to Create a Shared Suite: Create a new test suite (e.g., Playground Staging ). Configure the new suite's settings independently. Use the inheritance feature to pull in test cases, test data, and reusable rules from the parent suite. Inheritance Details: Test cases and rules from the parent suite can be inherited but not modified in the child suite. Test data can be overridden in the child suite, allowing for environment-specific values. Test cases can be disabled in the child suite to exclude them from execution. Best Practices: Avoid double inheritance; only single inheritance is allowed. Clearly label parent test suites for easy identification. In summary, shared suites facilitate efficient testing across multiple environments by allowing inheritance and modification of test data while maintaining the integrity of test cases and rules.