Testing with SaaS
Allow 30–45 minutes, plus your environment's asset processing time, to test the installed Windows app with AEM as a Cloud Service Author. Use an approved test environment. These are expected results to check, not an assurance that every Cloud operation is supported by the supplied build.
Add your License
For removal, device transfers and local file details, read Licensing.
- Install the supplied tester build and open Sambafied.
- Open About, then Manage licence.
- Enter the licence key supplied by Sambafied or your reseller and choose Activate.
- Confirm a valid activation for this device. Close and reopen licence management to check that activation was retained.
The Sambafied licence does not grant Adobe account access. Never include the key in screenshots or reports. If activation fails, record the redacted error and mark dependent tests Blocked. If an evaluation build omits licensing, confirm and record that exception with the test coordinator rather than marking it passed.

Illustrative sample. Manage licence confirms activation and shows the offline expiry.
Download the sample files
Download the sample ZIP pack (about 19 KB), or download files individually:
Extract the ZIP into an ordinary local folder before testing. For an individual
file, use your browser's Save link as if it opens a preview. Upload
sample-editable.txt through AEM's browser interface to your dedicated test DAM
folder and confirm it shows Revision: 1. Open the connected copy in Windows
Notepad, change it to Revision: 2, save and close, then verify a fresh original
downloaded from AEM. The image and PDF are also marked Revision 1. If your AEM
configuration rejects a sample file type, record that restriction as Blocked.
Prepare the test
Use your Cloud Service Author URL. For example:
https://author-p999999-e9999999.adobeaemcloud.com/
This is an example address. Replace p999999 and e9999999 with the project and
environment identifiers from your actual Author URL, or copy the complete URL
supplied by your AEM administrator. Use the Author endpoint, not a delivery URL.
- Record the app build, Windows version, Cloud Author URL, organization and test account.
- Confirm that the account can browse, download, create and update assets in a dedicated test DAM subtree through AEM's browser interface.
- Follow Connect to AEM Cloud Service. Use the Author URL, a separate connection and a distinct work folder. Enable Automatic upload for that connection.
- Create a folder such as
desktop-test-YYYYMMDD-initials. Use the sample image, PDF and editable text file above, or your own disposable equivalents. Seed the editable file in AEM with revision1. - Confirm the build's enabled Cloud operations and known issues with the coordinator. Record missing prerequisites as Blocked, not passed.
- Agree separate maximum waits for transfer and AEM processing. Record both timings; upload completion alone does not prove the asset is ready.
Run the main scenarios
| ID | Steps | Expected result |
|---|---|---|
| SAAS-01 Sign in | Add the Cloud Author connection. Complete Sign in with Adobe, organization SSO and MFA when requested. | Login remains available while needed. The app validates the Author session and displays the correct account, environment and work folder. |
| SAAS-02 Browse and search | Navigate to the test folder, search for a seeded asset and inspect preview/details. | Assets belong to the intended environment. Loading ends with real results or an understandable error. |
| SAAS-03 Open original | Use Open Drive and open the revision 1 asset from Explorer. | The actual original downloads and opens in the expected application with correct content. Check the mapped drive's Status column. |
| SAAS-04 Edit and save | Change to revision 2, save and close the editor. Independently download the original through Cloud Author into a separate folder. | Automatic upload completes and the downloaded original shows revision 2. Record transfer completion separately from AEM processing/readiness. |
| SAAS-05 Repeated saves | Save two further revisions, then close the editor and check a fresh Cloud Author download. | The final revision reaches the correct asset. Pending indicators settle without repeatedly uploading unchanged content. |
| SAAS-06 New uploads | Copy the image and PDF into a new subfolder in the connected work folder. | The folder and assets appear in Cloud Author. Independently downloaded originals match. Processing reaches a usable state; thumbnails/previews become available for supported formats. |
| SAAS-07 Changes from Author | Upload a new asset through Cloud Author and replace an existing test original after closing its local editor. | The desktop/Explorer view receives both changes. Opening the updated original shows the new revision. Record propagation and processing time separately. |
| SAAS-08 Rename and move | Rename a disposable asset in Explorer, then move it between test subfolders. Check Cloud Author after each step. | The intended remote path contains intact content without duplicate or abandoned assets. Record explicit unsupported-operation messages. |
| SAAS-09 Offline recovery | Disconnect only the test PC from the network. Edit a previously downloaded asset and save, then reconnect. | Local edits survive, unavailable/pending state is clear and final bytes reach Cloud Author after reconnecting without manual re-copying. |
| SAAS-10 Restart | Save another edit, quit the desktop app and reopen it. Reauthenticate if requested. | Connection settings and local content survive. Pending synchronization resumes or has finished; Cloud Author contains the final revision. |
| SAAS-11 Download a copy | Download the same asset twice to an ordinary local destination. | Both copies open with correct content, have distinct names and preserve existing files. |
| SAAS-12 Sign out and return | Wait for transfers to finish and close editors. Sign out of the Cloud connection, then sign in again. | The app shows a signed-out state without claiming new authenticated work succeeded. Existing local content survives; signing in restores the correct connection. |
Additional checks
- SSO cancellation/session expiry: Cancel sign-in once, then retry. If an approved test session expires naturally, check that reauthentication is clear and pending edits survive. Do not change organization identity settings to force expiry.
- Conflict: Edit a downloaded asset offline while a second tester replaces its Cloud Author original. Reconnect and check that both versions remain recoverable and conflict resolution is explained.
- Environment isolation: With separate local and Cloud connections, edit a disposable asset in one work folder. Verify that only its owning Author changes.
Record results and finish
Record Pass / Fail / Blocked / Not run for each ID and licence activation. Include the build, Author environment, asset path, timings and redacted errors or screenshots. Exclude licence keys, passwords, session cookies and signed URLs. An unsupported operation is not a pass; ask the coordinator to assess its scope.
Preserve failed-case assets and recovery copies until investigated. After results are accepted, remove only your disposable test assets. Keep existing work folders and application data. A local AEM pass or successful Cloud sign-in does not prove Cloud reads, uploads or processing: report each observed result separately.
See Testing with OnPrem and readiness and limits.