MokoConsulting/MokoJoomBackup
1
0
Fork 0
Code Issues 22 Pull Requests 1 Packages Projects Releases 1 Wiki Activity

Test: restore engine — full restore, partial restore, config preservation #4

New Issue
Open
opened 2026-06-02 20:29:21 +00:00 by jmiller · 1 comment
jmiller commented 2026-06-02 20:29:21 +00:00
Owner
Copy Link
Copy Source

Verify RestoreEngine correctly restores from backup archives.

Scope

  • Full restore (files + database)
  • Files-only restore
  • Database-only restore
  • configuration.php preservation
  • Staging directory cleanup

Acceptance Criteria

  • Full restore overwrites files and reimports database
  • configuration.php is preserved with current DB credentials
  • Partial restores (files-only, db-only) work correctly
  • Staging directory is cleaned up after restore
  • Failed restore preserves configuration.php
Verify RestoreEngine correctly restores from backup archives. ## Scope - Full restore (files + database) - Files-only restore - Database-only restore - configuration.php preservation - Staging directory cleanup ## Acceptance Criteria - [ ] Full restore overwrites files and reimports database - [ ] configuration.php is preserved with current DB credentials - [ ] Partial restores (files-only, db-only) work correctly - [ ] Staging directory is cleaned up after restore - [ ] Failed restore preserves configuration.php
jmiller added the type: testingpriority: criticalcomponent: enginestatus: ready labels 2026-06-02 20:29:21 +00:00
jmiller commented 2026-06-02 20:29:21 +00:00
Author
Owner
Copy Link
Copy Source

Testing Plan

Pre-requisites

  • Working backup archive from a known-good state
  • Test database that can be safely overwritten

TC-4.1: Full restore

  1. Make a backup of a site with known content
  2. Modify some articles and delete a file
  3. Run restore from the backup
  4. Verify articles are back to original state
  5. Verify deleted file is restored
  6. Verify configuration.php has CURRENT db credentials (not backup's)

TC-4.2: Files-only restore

  1. Run restore with restore_db=false
  2. Verify files are restored
  3. Verify database is unchanged

TC-4.3: Database-only restore

  1. Run restore with restore_files=false
  2. Verify database is restored
  3. Verify files are unchanged

TC-4.4: Config preservation

  1. Backup site A with db credentials for server A
  2. Restore to site B with different db credentials
  3. Verify configuration.php keeps site B's credentials

TC-4.5: Failed restore cleanup

  1. Corrupt a backup ZIP file
  2. Attempt restore
  3. Verify error message, staging dir cleaned up
  4. Verify configuration.php unchanged

TC-4.6: Protected files

  1. Verify .htaccess at root is NOT overwritten during restore
  2. Verify database.sql is NOT extracted to site root
## Testing Plan ### Pre-requisites - Working backup archive from a known-good state - Test database that can be safely overwritten **TC-4.1: Full restore** 1. Make a backup of a site with known content 2. Modify some articles and delete a file 3. Run restore from the backup 4. Verify articles are back to original state 5. Verify deleted file is restored 6. Verify configuration.php has CURRENT db credentials (not backup's) **TC-4.2: Files-only restore** 1. Run restore with restore_db=false 2. Verify files are restored 3. Verify database is unchanged **TC-4.3: Database-only restore** 1. Run restore with restore_files=false 2. Verify database is restored 3. Verify files are unchanged **TC-4.4: Config preservation** 1. Backup site A with db credentials for server A 2. Restore to site B with different db credentials 3. Verify configuration.php keeps site B's credentials **TC-4.5: Failed restore cleanup** 1. Corrupt a backup ZIP file 2. Attempt restore 3. Verify error message, staging dir cleaned up 4. Verify configuration.php unchanged **TC-4.6: Protected files** 1. Verify .htaccess at root is NOT overwritten during restore 2. Verify database.sql is NOT extracted to site root
Sign in to join this conversation.
Labels
Clear labels
component: admin
Admin UI and views
 component: api
REST API
 component: engine
Backup/restore engine
 component: remote
Remote storage (FTP/GDrive)
 component: scheduler
Scheduled tasks
 priority: critical
Must fix before release
 priority: high
Important for release
 priority: low
Nice to have
 priority: medium
Normal priority
 status: blocked
Blocked by dependency
 status: ready
Ready for development
 type: bug
Something is broken
 type: docs
Documentation
 type: feature
New feature or enhancement
 type: testing
Testing and QA
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels component: engine priority: critical status: ready type: testing
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomBackup#4
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?