How-To: Use EZCA Test Slots

How Does Keytos Test and Release New Features in EZCA?

EZCA follows a safe deployment pipeline (SDP) release process, where we gradually roll out new features and updates. Every code change goes through multiple stages of testing and validation before it reaches the production environment:

1. Development: Initial development and inner loop testing.
2. Testing: Changes are deployed to a test environment for validation and verification.
3. Code Review: Changes are reviewed and approved by peers, managers, and automated systems before they are merged into the main codebase.
4. Staging: Recently merged changes are deployed to a staging environment that closely mirrors the production environment (with separate infrastructure and data) for final validation before release.
5. Test Slots: Releases begin in test slots, allowing both internal and external users, as well as automated validation systems, to interact with upcoming features and provide feedback before they are officially released.
6. Production: Changes are finally deployed to the production environment after passing all previous stages of testing and validation.

Overview of EZCA Test Slots

Test slots are deployments of the next version of EZCA that allow users to interact with upcoming features and updates before they are officially released to all users. They are still considered as production environments, meaning they are subject to the same security, compliance, and operational standards as the live production environment, and any changes made within test slots are also reflected in your production endpoints. We make them available to both internal and external users for testing and feedback purposes.

What are the Test Slot Endpoints?

EZCA provides pre-production test slot endpoints for different regions, allowing users to test upcoming features and updates before they are deployed to the production environment.

Why Would I Use a Test Slot?

Test slots are useful for interacting with upcoming EZCA releases and testing new features before they are officially deployed to the production environment. They allow you to validate changes, perform canary testing, and ensure that new features work as expected before they are rolled out to the full production environment.

How Can I Use EZCA Test Slots?

To use a test slot, simply replace your existing production endpoint URLs with the corresponding test slot endpoint URLs from the table above. This allows you to interact with the test slot environment while keeping your production environment unchanged.

Does a Test Slot Use My Production Data?

Yes. While test slots run as a separate process from the production environment, they are still considered as production environments and will interact with your production certificate authorities and your data. Any changes made in the test slot will affect your production data, so it is important to exercise caution when testing new features or updates.

If you want to avoid affecting your production data while testing in a test slot, it is recommended to use separate subscriptions and certificate authorities for the test slot environment. This ensures that any changes made during testing do not impact your production data. You are responsible for managing and isolating your test slot environment to prevent unintended consequences on your production environment.

Does a Test Slot Have the Same SLA as the Production Environment?

No. Test slots do not have the same service level agreement (SLA) as the production environment. They are intended for testing and validation purposes, and their availability and performance may differ from the production environment. Do not rely on test slots for critical production workloads.

How Quickly Does a Release Move From a Test Slot to Production?

For nearly all releases, there is a minimum 24 hour bake time between a release being available in the test slot and it being deployed to the production environment. This allows sufficient time for testing and validation in the test slot before the release goes live in production.

For changes to critical components or features, additional time may be added before the release can be promoted from the test slot to production.

For security vulnerabilities, a faster promotion from the test slot to production may be implemented to address critical vulnerabilities promptly.

What if Something Breaks in a Test Slot?

If you encounter issues or something breaks when testing against a test slot, it is important to report the problem to the EZCA support team immediately by opening a support ticket in your production EZCA portal. Since test slots share production data, any issues could potentially impact your production environment. Always exercise caution and follow best practices when testing new features or updates in a test slot. You are responsible for any impact your testing may have on your production environment and data.