Test: Google Drive remote upload #7

Open
opened 2026-06-02 20:29:23 +00:00 by jmiller · 1 comment
Owner

Verify Google Drive uploader works with OAuth2 and resumable uploads.

Scope

  • OAuth2 token refresh
  • Resumable upload with chunking
  • Folder targeting
  • Error handling (expired tokens, wrong folder ID)
  • Connection test

Acceptance Criteria

  • Backup uploads to Google Drive folder
  • Large files upload via 5 MB chunks
  • Access token refreshes automatically
  • Connection test returns user email
  • Invalid credentials reported clearly
Verify Google Drive uploader works with OAuth2 and resumable uploads. ## Scope - OAuth2 token refresh - Resumable upload with chunking - Folder targeting - Error handling (expired tokens, wrong folder ID) - Connection test ## Acceptance Criteria - [ ] Backup uploads to Google Drive folder - [ ] Large files upload via 5 MB chunks - [ ] Access token refreshes automatically - [ ] Connection test returns user email - [ ] Invalid credentials reported clearly
jmiller added the type: testingpriority: highcomponent: remotestatus: ready labels 2026-06-02 20:29:23 +00:00
Author
Owner

Testing Plan

Pre-requisites

  • Google Cloud project with Drive API enabled
  • OAuth2 client credentials (client ID + secret)
  • Valid refresh token
  • Target folder ID in Google Drive

TC-7.1: Basic upload

  1. Configure profile with Google Drive credentials and folder ID
  2. Run backup
  3. Verify file appears in Google Drive folder
  4. Verify backup record shows remote_filename with gdrive:// path

TC-7.2: Large file chunking

  1. Create a backup > 10 MB
  2. Run with Google Drive upload
  3. Verify upload completes (multiple chunks)
  4. Verify file size in Drive matches local

TC-7.3: Token refresh

  1. Use a valid refresh token
  2. Run upload
  3. Verify access token is obtained automatically

TC-7.4: Invalid credentials

  1. Set wrong client_secret
  2. Run backup
  3. Verify upload fails with clear error
  4. Verify local backup preserved

TC-7.5: Connection test

  1. Use testConnection() method
  2. Verify it returns success with authenticated user email

TC-7.6: Wrong folder ID

  1. Set a non-existent folder ID
  2. Run backup
  3. Verify upload fails with permission/not-found error
## Testing Plan ### Pre-requisites - Google Cloud project with Drive API enabled - OAuth2 client credentials (client ID + secret) - Valid refresh token - Target folder ID in Google Drive **TC-7.1: Basic upload** 1. Configure profile with Google Drive credentials and folder ID 2. Run backup 3. Verify file appears in Google Drive folder 4. Verify backup record shows remote_filename with gdrive:// path **TC-7.2: Large file chunking** 1. Create a backup > 10 MB 2. Run with Google Drive upload 3. Verify upload completes (multiple chunks) 4. Verify file size in Drive matches local **TC-7.3: Token refresh** 1. Use a valid refresh token 2. Run upload 3. Verify access token is obtained automatically **TC-7.4: Invalid credentials** 1. Set wrong client_secret 2. Run backup 3. Verify upload fails with clear error 4. Verify local backup preserved **TC-7.5: Connection test** 1. Use testConnection() method 2. Verify it returns success with authenticated user email **TC-7.6: Wrong folder ID** 1. Set a non-existent folder ID 2. Run backup 3. Verify upload fails with permission/not-found error
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomBackup#7