ben/upskill-event-manager
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
upskill-event-manager/docs/staging-restore-plan.md
bengizmo cade20aa2b feat(testing): Implement HVAC Role Manager component 
- Added HVAC_Role_Manager class with role/permission management
- Implemented test cases in HVAC_Role_Manager_Test.php
- Created API documentation in docs/role-manager-api.md
- Updated testing improvement plan with progress
- Added design decisions to memory-bank/decisionLog.md

Includes:
- Role creation/deletion methods
- Permission management system
- Role conflict detection
- Permission inheritance logic
- Comprehensive test coverage
2025-04-14 19:02:22 -03:00

2 KiB
Raw Blame History

Staging Environment Restoration Plan

Overview

This plan outlines the steps to verify and complete the staging environment restoration after the production sync.

Prerequisites

  • Production sync has been completed ✓
  • Staging server details:
    • URL: wordpress-974670-5399585.cloudwaysapps.com
    • IP: 146.190.76.204
    • Path: /home/974670.cloudwaysapps.com/uberrxmprk/public_html

Verification Steps

1. Run Staging Verification

./bin/verify-staging.sh

This will:

  • Verify plugin activation
  • Check plugin status
  • Review debug logs
  • Verify required pages exist

2. Manual URL Verification

Check the following URLs:

3. Configure PHPUnit Environment

Configure PHPUnit for test execution:

./bin/configure-phpunit-staging.sh

This will:

  • Configure PHPUnit path in staging environment
  • Verify PHPUnit installation
  • Set up test environment variables

4. Run Basic Smoke Tests

Execute the basic smoke test suite to verify core functionality:

./bin/run-staging-tests.sh

Success Criteria

  • verify-staging.sh completes without errors
  • All URLs are accessible
  • PHPUnit configuration successful
  • Basic smoke tests pass
  • Plugin is active and functioning
  • No critical errors in debug.log

Rollback Plan

If issues are encountered:

  1. Document the specific failure
  2. Check debug logs for errors
  3. Consult with team for production sync retry if needed

Notes

  • All production syncs must be coordinated with the user
  • Monitor debug.log for any warnings or errors
  • Document any issues encountered in the process
  • PHPUnit tests can be run using either global command or vendor path
  • Test results are stored in tests/test-results/ directory