Validation Suites¶

Starting Point¶

Full Validation Suite¶

Phase 1: Admin Baseline¶

Log in as Admin.

Open Google Client application
Confirm Google Drive integration is configured and validates successfully
Confirm Gemini / Agent Platform / Vertex is not configured
Confirm AI summary / Q&A features are not active
Confirm folder structure is set to No folder structure / Default folder only
Open configuration tabs and confirm there are no page-level errors
Confirm admin-only configuration pages are available to the admin user
Confirm Analytics tab renders for the admin user
Confirm Logger Admin Dashboard renders for the admin user

Phase 2: Core Cloud Uploads¶

Log in as Internal User A.

Use Record A.

Use the Lightning record page that contains both Google Client record components:

Uploader component
Attachments component

Run the full file-type upload set from the Uploader component first. Files uploaded from the Uploader component should be validated from the Uploader component. Do not assume they appear in the Attachments component.

Phase 3: Uploader Preview and File Actions¶

Continue as Internal User A.

Use the files uploaded through the Uploader component in Phase 2.

Use the Uploader component as the main entry point for Preview in this phase. Do not use the Attachments component for these Uploader-uploaded files.

Phase 4: Attachments Preview and File Actions¶

Continue as Internal User A.

Use only files uploaded through the Attachments component.

Use the Attachments component as the entry point for Preview in this phase. Do not use Uploader-uploaded files for Attachments-specific checks.

Phase 5: File Explorer¶

Continue as Internal User A.

Use the File Explorer Lightning tab only for this phase. Do not use the record page Uploader or Attachments components for File Explorer-specific checks.

Open File Explorer
Confirm Owned files tab renders correctly
Confirm Shared files tab renders correctly
Confirm files uploaded from the Uploader component appear under Owned files where expected
Confirm files uploaded from the Attachments component appear under Owned files where expected
Open Preview from File Explorer
Upload a file from the File Explorer upload action
Confirm the file uploaded from File Explorer appears in File Explorer
Confirm the file uploaded from File Explorer is placed in the expected default/root Google Drive folder

Continue as Internal User A.

Use one owned file that was uploaded through the Attachments component on Record A.

Use the Attachments component on Record A to open Preview and Share.

Open Preview from the Attachments component
Open Share modal from Preview
Share the file with Internal User B as Viewer
Confirm sharing completes successfully

Log in as Internal User B.

Use the Attachments component on Record A to verify access.

Log in as Internal User A.

Use the Attachments component on Record A.

Open Share modal again from Preview
Change Internal User B access to Collaborator or equivalent edit-level access
Confirm sharing update completes successfully

Log in as Internal User B.

Use the Attachments component on Record A.

Open Preview for the shared file from the Attachments component
Confirm Edit behavior is applied
Confirm collaborator can upload a new version
Confirm collaborator can edit details

Phase 7: Public Link¶

Log in as Internal User A.

Use one owned file that was uploaded through the Attachments component.

Use the Attachments component on Record A to open Preview and Public Link.

Open Preview from the Attachments component
Open Public Link modal from Preview
Create a public link
Open the link in a separate browser/session without Salesforce login
Confirm the public link opens successfully
Revoke the public link
Create a public link & set an expiration date
Confirm the link no longer works after the expiration date

Phase 8: Attach Existing Files¶

Log in as Internal User A.

Use these records:

Record A: original linked record
Record B: additional linked record
Record C: unrelated record

Use the Attachments component for Attach Existing Files. Do not use the Uploader component for this phase.

Phase 9: Multi-Record Security¶

Use the file linked to Record A and Record B.

Use the Attachments component on each record to validate record-based visibility.

Log in as a user who has access to Record A only.

Confirm the file is visible on Record A in the Attachments component
Confirm the file is not visible from unrelated Record C in the Attachments component
Open Preview from the Attachments component on Record A
Confirm resolved access level matches Record A access

Log in as a user who has access to Record B only.

Confirm the file is visible on Record B in the Attachments component
Confirm the file is not visible from unrelated Record C in the Attachments component
Open Preview from the Attachments component on Record B
Confirm resolved access level matches Record B access

Log in as a user who has access to Record C only.

Confirm the file is not visible on Record C in the Attachments component
Confirm the file is not returned in search results
Confirm direct Preview URL does not open the file
Confirm direct File Details URL does not open the file
Confirm file actions cannot be executed from any entry point

Log in as Admin or record owner.

Remove the association between the file and Record A
Confirm users with access only to Record A no longer have record-based access
Confirm users with access to Record B still have access

Phase 10: File Record Details Page¶

Log in as Internal User A.

Use the File Record Details page directly for this phase.

Open File Record Details page for an owned file
Confirm file details display correctly
Confirm linked records component renders correctly
Confirm linked records are shown only when the current user has access to those records
Confirm file actions respect the current user's resolved access level
Open File Record Details page for a file the current user should not access
Confirm access is denied or safe fallback behavior is shown

Phase 11: Experience Cloud¶

Log in as External User E.

Use the Experience Cloud test record.

Use the Experience Cloud Uploader component for upload checks and the Experience Cloud Attachments component for file list, View All, and Preview checks.

Log in as Internal User A.

Use the internal Core Cloud Attachments component on the Experience Cloud test record.

[X ] Open Share modal for a file linked to the Experience Cloud record from Preview
Enable external visibility for the related record
Save sharing changes

Log in as External User E.

Use the Experience Cloud Attachments component.

Refresh the Experience Cloud record page
Confirm the externally visible file appears in the Experience Cloud Attachments component
Open Preview from the Experience Cloud Attachments component
Confirm Viewer behavior where expected
Confirm unrelated linked records are not exposed

Phase 12: Folder Structure¶

For each folder structure configuration, log in as Admin first, change the folder structure, then log in as Internal User A and validate upload/attach behavior.

Use these component rules for this phase:

Record-page Uploader component validates upload behavior from Uploader and Uploader-only file visibility
Record-page Attachments component validates upload behavior from Attachments, Attachments-only file visibility, and Attach Existing Files
File Explorer validates File Explorer upload behavior separately

No Folder Structure / Default Folder Only¶

Log in as Admin.

Configure No folder structure / Default folder only

Log in as Internal User A.

Upload a file from the Uploader component
Confirm the file appears in the Uploader component
Upload a file from the Attachments component
Confirm the file appears in the Attachments component
Upload a file from File Explorer
Confirm the file appears in File Explorer
Confirm files uploaded from Uploader, Attachments, and File Explorer are placed in the default/root configured folder
Attach an existing file to another record using Attach Existing Files from the Attachments component
Confirm no record-specific or user-specific folder is created

Folder per Record¶

Log in as Admin.

Configure Folder per Record

Log in as Internal User A.

Folder per User¶

Log in as Admin.

Configure Folder per User

Log in as Internal User A.

Log in as Internal User B.

Upload a file from the Uploader component
Confirm the file appears in the Uploader component
Confirm file is placed under Internal User B folder
Upload a file from the Attachments component
Confirm the file appears in the Attachments component
Confirm Attachments upload is placed under Internal User B folder
Confirm Internal User A and Internal User B use different user folders

Folder per Record → User¶

Log in as Admin.

Configure Folder per Record → User

Log in as Internal User A.

Upload a file to a record using the Uploader component
Confirm the file appears in the Uploader component
Confirm file is placed under Record → User path
Upload a file to the same record using the Attachments component
Confirm the file appears in the Attachments component
Confirm Attachments upload is placed under the same Record → User path
Attach an existing file to another record using Attach Existing Files from the Attachments component
Confirm expected Drive representation is created under the target Record → User path

Log in as Internal User B.

Upload a file to the same record using the Uploader component
Confirm the file appears in the Uploader component
Confirm Internal User B uses a separate user folder under the same record folder

Folder per User → Record¶

Log in as Admin.

Configure Folder per User → Record

Log in as Internal User A.

Phase 13: Delete and Cleanup¶

Log in as Internal User A.

Use a file linked to multiple records.

Confirm file appears on all linked records in the Attachments/Uploader component
Delete the file from Preview or supported file action
Confirm the file is removed from all linked records & Google Drive

Phase 14: Gemini Configuration¶

Log in as Admin.

Log in as Internal User A.

Log in as Admin.

Disable the Enable AI File Intelligence setting

Log in as Internal User A.

Use Preview opened from the same component where the files were uploaded.

Open Preview for the file
Confirm AI File Intelligence actions are not available after the setting is disabled
Upload another new file after Enable AI File Intelligence is disabled
Confirm no new summary is generated for files uploaded while Enable AI File Intelligence is disabled

Phase 15: Agent Platform / Vertex Configuration¶

Log in as Admin.

Disable or clear Gemini configuration where needed
Configure Agent Platform / Vertex
Validate Agent Platform / Vertex configuration
Configure summary prompt
Configure question-answering prompt
Configure token limits
Enable the Enable AI File Intelligence setting

Log in as Internal User A.

Log in as Admin.

Disable the Enable AI File Intelligence setting

Log in as Internal User A.

Use Preview opened from the same component where the file was uploaded.

Confirm AI File Intelligence actions are not available while Agent Platform / Vertex remains configured but Enable AI File Intelligence is disabled
Upload another new file after Enable AI File Intelligence is disabled
Confirm no new summary is generated for files uploaded while Enable AI File Intelligence is disabled

Phase 16: Admin and Permission Checks¶

Log in as Admin-level non-system user without View All Data, but with Google Client Admin permission.

Open Google Client admin functionality available to Google Client admins
Open Analytics tab
Confirm Logger Admin Dashboard renders where expected
Confirm admin user cannot perform day-to-day file operations from Uploader, Attachments, File Explorer, or Preview unless user permissions are also assigned

Log in as regular operational user without admin permissions.

Confirm admin configuration pages are not accessible
Confirm Analytics dashboard is not accessible
Confirm operational file features still work from Uploader, Attachments, File Explorer, and Preview where user has record/file access

Phase 17: Final Sweep¶

Use the final intended release configuration.

Quick Regression Suite¶

Use this when changes are small and isolated, but you still want confidence across the main flows.

Phase 1: Admin Baseline¶

Log in as Admin.

Confirm Google Drive integration is configured and validated
Confirm current folder structure configuration is known
Confirm current AI provider configuration is known
Confirm the Enable AI File Intelligence checkbox state is known
Open Google Client app and confirm configuration tabs render without errors

Phase 2: Upload and Preview¶

Log in as Internal User A.

Use Record A.

Use both record-page components in this phase:

Phase 3: Versioning¶

Continue as Internal User A.

Use Preview opened from the same component where the previewable file was uploaded.

Upload a new version for the previewable file from Preview
Confirm the latest version becomes active
Confirm Preview uses the expected latest version
Confirm Download uses the expected latest version

Continue as Internal User A.

Use a file from the component where it is visible.

Open Preview from the component where the file is visible
Share the file with Internal User B as Viewer from Preview

Log in as Internal User B.

Use the same component path where the shared file is expected to appear.

Open the same record
Confirm the shared file is visible in the expected component
Open Preview from the expected component
Confirm read-only behavior
Confirm download works
Confirm edit/version/delete/share/public link actions are not available

Phase 5: Attach Existing File¶

Log in as Internal User A.

Use the Attachments component.

Open another Salesforce record
Open Attach Existing Files from the Attachments component
Confirm owned files are available
Attach an existing owned file
Confirm the file appears on the second record in the Attachments component
Confirm the same file still appears on the original record in the Attachments component where expected
Confirm File Record Details shows linked records where available

Phase 6: Access¶

Use a file linked to two records.

Use the component where the file is expected to be visible for record-level visibility and Preview access checks.

Confirm a user with access to a linked record can see the file in the expected component
Confirm a user with access only to an unrelated record cannot see the file in the expected component
Confirm direct Preview URL does not bypass access checks
Confirm direct File Details URL does not bypass access checks

Phase 7: Folder Structure¶

Use the currently configured folder structure.

Use the Uploader component, Attachments component, and Attach Existing Files flow explicitly in this phase.

Upload one file from the Uploader component
Confirm the file appears in the Uploader component
Upload one file from the Attachments component
Confirm the file appears in the Attachments component
Confirm files are placed in the expected Google Drive folder
Attach an existing file to another record using Attach Existing Files from the Attachments component
Confirm Drive placement or shortcut behavior matches the configured folder structure

If the release touched File Explorer upload or folder placement logic, also run this File Explorer check.

Upload one file from File Explorer
Confirm the file appears in File Explorer
Confirm File Explorer upload uses the expected Google Drive folder

If the release touched folder structure logic, also run this reduced folder matrix.

Phase 8: Experience Cloud¶

Log in as External User E.

Use Experience Cloud components only for this phase.

Open Experience Cloud page containing Google Client Uploader and Attachments components
Confirm Experience Cloud Uploader component renders without errors
Confirm Experience Cloud Attachments component renders without errors
Confirm files are hidden in the Experience Cloud Attachments component by default unless external visibility is enabled
Open a visible file from the Experience Cloud Attachments component
Confirm Preview works
Confirm external user sees only allowed actions

Phase 9: AI¶

Run this phase only if AI configuration or AI-related UI was touched.

Log in as Admin.

Confirm Gemini or Agent Platform / Vertex configuration is available
Confirm the Enable AI File Intelligence checkbox is in the expected state
Confirm prompts and token limits can be saved

Log in as Internal User A.

Use the component where the file should be validated.

Files uploaded before Enable AI File Intelligence was enabled are not expected to receive summaries.

If Enable AI File Intelligence is enabled, upload a new file with clear business content from the component being tested
Confirm the new file appears in the same component where it was uploaded
Open Preview for the new file from the same component
Confirm summary behavior matches the current AI provider and Enable AI File Intelligence setting
Confirm hover behavior matches the current AI provider and Enable AI File Intelligence setting in Uploader where supported
Confirm hover behavior matches the current AI provider and Enable AI File Intelligence setting in Attachments where supported
If Enable AI File Intelligence is enabled, confirm question answering works from Preview for files uploaded after the setting was enabled
If Enable AI File Intelligence is disabled, confirm question answering is not available from Preview
If Enable AI File Intelligence is disabled, confirm no new summary is generated for files uploaded while the setting is disabled

Phase 10: Final Smoke Check¶

Internal user can open Core Cloud record pages without errors
External user can open Experience Cloud pages without errors
Admin can open Google Client app without errors
Uploader component works where expected
Attachments component works where expected
File Explorer works where expected
No critical errors appear in the UI
No critical errors appear in logs

Targeted Regression Suite¶

Use this when you want to validate what was added/changed, without running a full suite.

Validation Suites¶

Starting Point¶

Full Validation Suite¶

Phase 1: Admin Baseline¶

Phase 2: Core Cloud Uploads¶

Phase 3: Uploader Preview and File Actions¶

Phase 4: Attachments Preview and File Actions¶

Phase 5: File Explorer¶

Phase 6: Internal Sharing¶

Phase 7: Public Link¶

Phase 8: Attach Existing Files¶

Phase 9: Multi-Record Security¶

Phase 10: File Record Details Page¶

Phase 11: Experience Cloud¶

Phase 12: Folder Structure¶

No Folder Structure / Default Folder Only¶

Folder per Record¶

Folder per User¶

Folder per Record → User¶

Folder per User → Record¶

Phase 13: Delete and Cleanup¶

Phase 14: Gemini Configuration¶

Phase 15: Agent Platform / Vertex Configuration¶

Phase 16: Admin and Permission Checks¶

Phase 17: Final Sweep¶

Quick Regression Suite¶

Phase 1: Admin Baseline¶

Phase 2: Upload and Preview¶

Phase 3: Versioning¶

Phase 4: Internal Sharing¶

Phase 5: Attach Existing File¶

Phase 6: Access¶

Phase 7: Folder Structure¶

Phase 8: Experience Cloud¶

Phase 9: AI¶

Phase 10: Final Smoke Check¶

Targeted Regression Suite¶