Beta Testing

Learn how to test releases at 0% rollout with your internal team using Stallion's beta testing feature.

Beta Testing

Beta testing allows your internal team to test releases even when they're set to 0% rollout. This is particularly useful for testing new features or bug fixes before making them available to your entire user base.

How Beta Testing Works

When a release is promoted to production at 0% rollout, it's not distributed to regular users. However, internal team members can still receive these releases by logging into the Stallion testing interface.

Internal User Status

Once you log into the Stallion modal using the SDK access pin, your device is considered an "internal user." This special status allows you to receive releases that are set to 0% rollout, which are normally not distributed to regular users.

Accessing Beta Releases

Prerequisites

Prerequisite:

You need to have the Stallion SDK integrated and access to the SDK access pin. For detailed setup instructions, refer to Stallion Testing.

Step-by-Step Process

  1. Login to Stallion: Use the Stallion modal in your app with the SDK access pin
  2. Internal User Status: Once logged in, your device is considered an internal user
  3. Receive 0% Releases: Even releases set to 0% rollout will be downloaded to your device
  4. Test Thoroughly: You can test the release in a production-like environment before rolling out to users

Beta Testing Workflow

Complete Development and Deployment Process

The complete workflow for developing, testing, and deploying releases follows this sequence:

  1. Feature Development: Work on different features in your development environment
  2. Testing Framework: Use the Testing Framework to test individual features and components
  3. Release Preparation: Once features are ready, prepare a release for production
  4. Beta Testing: Test the complete release using beta testing at 0% rollout
  5. Phased Rollout: Use Phased Rollout to gradually deploy to your users

Beta Testing Process

  1. Promote Release: Promote your release to production with 0% rollout
  2. Internal Testing: Your team logs into the Stallion interface and tests the release
  3. Validate Changes: Ensure the release works correctly in the production environment
  4. Ready for Rollout: Once validated, the release is ready for phased rollout to users

Testing Best Practices

  • Test in Production Environment: Use the same environment your users will experience
  • Test All Features: Ensure all new functionality works as expected
  • Performance Testing: Check for any performance regressions
  • Edge Cases: Test various scenarios and edge cases
  • Device Compatibility: Test on different devices and screen sizes

Testing Strategy Overview

Three-Phase Testing Approach

Complete Testing Strategy:

For optimal release quality, follow this three-phase approach: Testing Framework → Beta Testing → Phased Rollout

Phase 1: Testing Framework

  • Purpose: Test individual features and components during development
  • Environment: Development and staging environments
  • Scope: Feature-specific testing and component validation
  • Documentation: Testing Framework

Phase 2: Beta Testing

  • Purpose: Test complete releases in production environment with internal team
  • Environment: Production environment with 0% rollout
  • Scope: End-to-end testing of the complete release
  • Access: Internal team members only

Phase 3: Phased Rollout

  • Purpose: Gradually deploy to users with controlled rollout percentages
  • Environment: Production environment with increasing rollout percentages
  • Scope: User-facing deployment with monitoring
  • Documentation: Phased Rollout

Benefits of Beta Testing

Quality Assurance

  • Production Environment Testing: Test releases in the actual production environment without affecting users
  • Complete Release Validation: Validate the entire release as a cohesive unit after individual feature testing
  • Real-World Testing: Test with real data and production conditions
  • Quality Gate: Final quality checkpoint before user deployment

Risk Mitigation

  • Controlled Testing: Test with a small, controlled internal team before wider release
  • Issue Detection: Identify integration issues that may not appear in individual feature testing
  • Production Readiness: Ensure the release is truly ready for production deployment
  • User Experience: Validate the complete user experience before public rollout

Workflow Integration

  • Bridge Between Testing and Deployment: Serves as the critical step between Testing Framework and Phased Rollout
  • Production Confidence: Provides confidence that the release works in production before user deployment
  • Team Alignment: Ensures your entire team has tested and approved the release
  • Deployment Readiness: Confirms the release is ready for gradual user rollout