mirror of
https://github.com/abraunegg/onedrive
synced 2026-03-14 14:35:46 +01:00
2.8 KiB
2.8 KiB
End to End Testing of OneDrive Client for Linux
| Test Case | Description | Details |
|---|---|---|
| 0001 | Basic Resync | - validate that the E2E framework can invoke the client - validate that the configured environment is sufficient to run a basic sync - provide a simple baseline smoke test before more advanced E2E scenarios |
| 0002 | 'sync_list' Validation | This validates sync_list as a policy-conformance test. The test is considered successful when all observed sync operations involving the fixture tree match the active sync_list rules. This test covers exclusions, inclusions, wildcard and globbing for paths and files. Specific 'sync_list' test coverage is as follows: - Scenario SL-0001: root directory include with trailing slash - Scenario SL-0002: root include without trailing slash - Scenario SL-0003: non-root include by name - Scenario SL-0004: include tree with nested exclusion - Scenario SL-0005: included tree with hidden directory excluded - Scenario SL-0006: file-specific include inside named directory - Scenario SL-0007: rooted include of Programming tree - Scenario SL-0008: exclude Android recursive build output and include Programming - Scenario SL-0009: exclude Android recursive .cxx content and include Programming - Scenario SL-0010: exclude Web recursive build output and include Programming - Scenario SL-0011: exclude .gradle anywhere and include Programming - Scenario SL-0012: exclude build/kotlin anywhere and include Programming - Scenario SL-0013: exclude .venv and venv anywhere and include Programming - Scenario SL-0014: exclude common cache and vendor directories and include Programming - Scenario SL-0015: complex style Programming ruleset - Scenario SL-0016: massive mixed rule set across Programming Documents and Work - Scenario SL-0017: stress test kitchen sink rule set with broad include and targeted file include - Scenario SL-0018: exact trailing slash configuration with cleanup validation - Scenario SL-0019: no trailing slash workaround with cleanup validation - Scenario SL-0020: focused trailing slash Projects regression for sibling path survival - Scenario SL-0021: focused no trailing slash Projects regression for sibling path survival - Scenario SL-0022: exact root-file include - Scenario SL-0023: sync_root_files = true with rooted 'Projects' include - Scenario SL-0024: cleanup regression with 'sync_root_files = true' - Scenario SL-0025: prefix-collision safety for 'Projects/Code' - Scenario SL-0026: mixed rooted subtree include plus exact root-file include |