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

Test: profile management CRUD and form validation #12

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

Verify backup profile creation, editing, and deletion works correctly.

Scope

  • Create profile with all fields
  • Edit existing profile
  • Delete profile
  • Form validation (required fields)
  • Default values
  • showon field visibility (FTP/GDrive conditional fields)

Acceptance Criteria

  • All form tabs render correctly
  • FTP fields show only when remote_storage=ftp
  • Google Drive fields show only when remote_storage=google_drive
  • Title is required
  • Default profile cannot be deleted
Verify backup profile creation, editing, and deletion works correctly. ## Scope - Create profile with all fields - Edit existing profile - Delete profile - Form validation (required fields) - Default values - showon field visibility (FTP/GDrive conditional fields) ## Acceptance Criteria - [ ] All form tabs render correctly - [ ] FTP fields show only when remote_storage=ftp - [ ] Google Drive fields show only when remote_storage=google_drive - [ ] Title is required - [ ] Default profile cannot be deleted
jmiller added the type: testingpriority: mediumcomponent: adminstatus: ready labels 2026-06-02 20:29:27 +00:00
jmiller commented 2026-06-02 20:29:27 +00:00
Author
Owner
Copy Link
Copy Source

Testing Plan

TC-12.1: Create profile

  1. Navigate to Profiles > New
  2. Fill in all tabs (General, Archive, Filters, Remote)
  3. Save
  4. Verify all values persisted correctly

TC-12.2: Edit profile

  1. Open existing profile
  2. Change backup_type, exclusion filters, compression
  3. Save and reopen
  4. Verify changes persisted

TC-12.3: Delete profile

  1. Select a non-default profile
  2. Click Delete
  3. Verify profile removed

TC-12.4: Required validation

  1. Try to save profile with empty title
  2. Verify validation error

TC-12.5: showon conditional fields

  1. Set remote_storage to "None" — verify FTP/GDrive fields hidden
  2. Set to "FTP" — verify FTP fields visible, GDrive hidden
  3. Set to "Google Drive" — verify GDrive fields visible, FTP hidden

TC-12.6: Default values

  1. Create new profile
  2. Verify defaults: type=full, format=zip, compression=5, backup_dir=default path
## Testing Plan **TC-12.1: Create profile** 1. Navigate to Profiles > New 2. Fill in all tabs (General, Archive, Filters, Remote) 3. Save 4. Verify all values persisted correctly **TC-12.2: Edit profile** 1. Open existing profile 2. Change backup_type, exclusion filters, compression 3. Save and reopen 4. Verify changes persisted **TC-12.3: Delete profile** 1. Select a non-default profile 2. Click Delete 3. Verify profile removed **TC-12.4: Required validation** 1. Try to save profile with empty title 2. Verify validation error **TC-12.5: showon conditional fields** 1. Set remote_storage to "None" — verify FTP/GDrive fields hidden 2. Set to "FTP" — verify FTP fields visible, GDrive hidden 3. Set to "Google Drive" — verify GDrive fields visible, FTP hidden **TC-12.6: Default values** 1. Create new profile 2. Verify defaults: type=full, format=zip, compression=5, backup_dir=default path
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: admin priority: medium 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#12
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?