Change Details

Future differentials will heavily use connection handling so testing it directly is redundant. To test WAL disabling we must actually use the whole stack: 1. Build WASM and run web app without this stack. 2. Apply this stack, re-build WASM and run web app again. Ensure not to clear site data or not to run tests in incognito mode! Otherwise you will only test WAL disabling upon fresh db creation but not the migration. 3. Ensure refreshing doesn't cause log-out/loss of data.

Future differentials will heavily use connection handling so testing it directly is redundant. To test WAL disabling we must actually use the whole stack: 1. Build WASM and run web app without this stack. 2. Apply this stack, re-build WASM and run web app again. Ensure not to clear site data or not to run tests in incognito mode! Otherwise you will only test WAL disabling upon fresh db creation but not the migration. 3. Ensure refreshing doesn't cause log-out/loss of data. Execute test plan for native app as well since WAL is also disabled there.

Future differentials will heavily use connection handling so testing it directly is redundant. To test WAL disabling we must actually use the whole stack: 1. Build WASM and run web app without this stack. 2. Apply this stack, re-build WASM and run web app again. Ensure not to clear site data or not to run tests in incognito mode! Otherwise you will only test WAL disabling upon fresh db creation but not the migration. 3. Ensure refreshing doesn't cause log-out/loss of data. Execute test plan for native app as well since WAL is also disabled there.