Skip to content

8.12. Post-Release Validation (Production Smoke Testing)

← Previous: Acceptance Testing | Back to Testing Workflow | Next: Defect Management →

After a successful deployment to the production environment, QA performs a limited set of validation checks to confirm that the application is functioning correctly in the live environment.

The goal of this phase is to ensure that the release was deployed successfully and that critical system functionality is operational for end users.

Production smoke test suites are designed to validate critical system functionality without impacting real user data.

Post-release validation is not mandatory for all projects and may be limited depending on system constraints and production risks. In such cases, validation relies on stakeholder feedback and real user behavior.

8.12.1 Objectives

  • Verify successful production deployment
  • Validate critical functionality in production
  • Confirm application accessibility
  • Identify critical production issues early
  • Provide deployment confirmation to stakeholders

8.12.2 Testing Environment

Testing is performed in the Production environment after deployment.

8.12.3 QA Activities

flowchart TB
    A["Production Deployment Completed"] --> B["Application Accessibility Check"]
    B --> C["Critical User Journey Validation"]
    C --> D["Integration Verification"]
    D --> E["New Feature Validation"]
    E --> F["UI & Navigation Check"]
    F --> G["Production Smoke Tests"]
    G --> H["Error Monitoring & Logs"]
    H --> I["Production Validation Result"]

    style A fill:#FFCDD2
    style B fill:#FF6D00
    style C fill:#FF6D00
    style D fill:#FFD600
    style E fill:#FFD600
    style F fill:#FFE0B2
    style G fill:#FFE0B2
    style H fill:#FFF9C4
    style I fill:#00C853
During this phase QA performs the following activities:

Application Accessibility Verification - verifying that the application is accessible and loads correctly - confirming the application responds appropriately - checking that login and authentication work - validating that the deployment completed successfully

Critical User Journey Validation - verifying critical user journeys (core product workflows) - testing key features in production environment - validating essential business processes - confirming critical functionality is operational

Integration Verification - confirming that key integrations with external systems function correctly - validating API connectivity - verifying third-party service connections - checking database connectivity

New Feature Validation - validating that newly released features are visible and operational - confirming new functionality behaves as expected - verifying feature flags or configurations - testing release-specific changes

UI and Navigation Verification - checking basic UI functionality on primary supported browsers or devices - validating that navigation works correctly - verifying key pages load properly - confirming no critical UI issues

Error Monitoring - confirming that no critical errors appear in the application interface - checking for console errors or warnings - monitoring error tracking systems - reviewing logs for critical issues

Production Smoke Test Suite Execution - executing dedicated production smoke test suites, which may include both automated and manual smoke test cases

QA may also monitor logs, error tracking tools, or monitoring systems to detect potential issues immediately after release.

8.12.4 Production Smoke Test Coverage

Production smoke tests typically validate:

  • Application Availability – system is accessible
  • Authentication – login/logout works
  • Core Features – critical functionality operational
  • Key Integrations – essential services respond
  • New Features – recently released features work
  • Data Operations – basic operations succeed
  • UI Rendering – key pages display correctly

8.12.5 Testing Considerations

Production Environment: - Use only production-safe test accounts - Avoid creating test data that affects real users - Follow data protection and privacy guidelines - Minimize impact on production systems - Use read-only operations where possible

Time Sensitivity: - Perform validation quickly after deployment - Provide rapid feedback to deployment team - Escalate critical issues immediately - Document findings in real-time

8.12.6 Entry Criteria

Before post-release validation begins:

  • Production deployment completed
  • Deployment confirmation received
  • Production smoke test suite prepared
  • Test accounts available (production-safe)
  • Access to production environment verified

8.12.7 Quality Gates

  • All production smoke tests are executed and results are documented
  • Critical functionality in production works correctly
  • No blocking/critical defects in production remain
  • Deployment is confirmed as successful
  • Status and results are communicated to stakeholders
  • New features are available and operational

8.12.8 Escalation

If critical issues are identified:

  1. Immediate Communication – alert deployment and development teams
  2. Issue Documentation – document the issue with details
  3. Impact Assessment – evaluate user impact
  4. Escalation – follow incident response procedures
  5. Resolution Tracking – monitor fix deployment

← Previous: Acceptance Testing | Back to Testing Workflow | Next: Defect Management →