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

Test: database dumper — table exclusions, special characters, large tables #2

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

Verify DatabaseDumper handles edge cases correctly.

Scope

  • Table exclusion filters (e.g. #__session)
  • Tables with special characters in data (unicode, quotes, NULLs)
  • Large tables (10k+ rows) with chunked export
  • Only site-prefix tables are included

Acceptance Criteria

  • Excluded tables not present in dump
  • Special characters preserved through dump/import cycle
  • Large tables export without memory exhaustion
  • Non-site-prefix tables are ignored
Verify DatabaseDumper handles edge cases correctly. ## Scope - Table exclusion filters (e.g. #__session) - Tables with special characters in data (unicode, quotes, NULLs) - Large tables (10k+ rows) with chunked export - Only site-prefix tables are included ## Acceptance Criteria - [ ] Excluded tables not present in dump - [ ] Special characters preserved through dump/import cycle - [ ] Large tables export without memory exhaustion - [ ] Non-site-prefix tables are ignored
jmiller added the type: testingpriority: highcomponent: enginestatus: ready labels 2026-06-02 20:29:19 +00:00
jmiller commented 2026-06-02 20:29:19 +00:00
Author
Owner
Copy Link
Copy Source

Testing Plan

TC-2.1: Table exclusion

  1. Add #__session and #__mail_queue to exclude list
  2. Run backup, open database.sql
  3. Verify neither table appears in dump
  4. Verify all other site tables ARE present

TC-2.2: Special characters

  1. Create an article with unicode (emojis, CJK), single quotes, backslashes, NULL fields
  2. Run backup
  3. Restore to a test database
  4. Verify article content matches original exactly

TC-2.3: Large tables

  1. Insert 10,000 rows into a test table
  2. Run backup, monitor PHP memory usage
  3. Verify all rows present in dump (chunked at 500 rows)
  4. Verify dump file is well-formed SQL

TC-2.4: Prefix isolation

  1. Create a table without the site prefix manually
  2. Run backup
  3. Verify that table is NOT in the dump
## Testing Plan **TC-2.1: Table exclusion** 1. Add `#__session` and `#__mail_queue` to exclude list 2. Run backup, open database.sql 3. Verify neither table appears in dump 4. Verify all other site tables ARE present **TC-2.2: Special characters** 1. Create an article with unicode (emojis, CJK), single quotes, backslashes, NULL fields 2. Run backup 3. Restore to a test database 4. Verify article content matches original exactly **TC-2.3: Large tables** 1. Insert 10,000 rows into a test table 2. Run backup, monitor PHP memory usage 3. Verify all rows present in dump (chunked at 500 rows) 4. Verify dump file is well-formed SQL **TC-2.4: Prefix isolation** 1. Create a table without the site prefix manually 2. Run backup 3. Verify that table is NOT in the dump
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: high 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#2
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?