notplants.bsky.social / git-remote-pds
⚘ use your pds as a git remote if you want to ⚘
5
fork

Configure Feed

Select the types of activity you want to include in your feed.

refactor test structure

notplants ec9e745b 437495e3

+11 -11
+2 -2
.gitignore
··· 1 1 /target 2 - scripts/pds-dev/pds-data/ 3 - scripts/pds-dev/pds.env 2 + e2e-tests/pds-dev/pds-data/ 3 + e2e-tests/pds-dev/pds.env 4 4 tests/.testenv 5 5 result 6 6 .venv
+6 -6
README.md
··· 175 175 End-to-end tests for the OAuth login and push flow using Playwright: 176 176 177 177 ```bash 178 - ./playwright-test/run.sh 178 + ./e2e-tests/playwright-tests/run.sh 179 179 ``` 180 180 181 181 Tests `oauth-login` with browser automation, then pushes and clones to verify. ··· 183 183 ### Local PDS (Docker) 184 184 185 185 ```bash 186 - ./scripts/pds-dev/start.sh # start PDS at localhost:3000 187 - ./scripts/pds-dev/create-account.sh alice secret123 # create a test account 188 - ./scripts/pds-dev/run-e2e.sh # full test harness 189 - ./scripts/pds-dev/stop.sh # tear down 186 + ./e2e-tests/pds-dev/start.sh # start PDS at localhost:3000 187 + ./e2e-tests/pds-dev/create-account.sh alice secret123 # create a test account 188 + ./e2e-tests/pds-dev/run-e2e.sh # full test harness 189 + ./e2e-tests/pds-dev/stop.sh # tear down 190 190 ``` 191 191 192 192 ### Remote PDS testing ··· 202 202 Then run: 203 203 204 204 ```bash 205 - ./scripts/remote-test/run.sh 205 + ./e2e-tests/remote-test/run.sh 206 206 ``` 207 207 208 208 This tests push, clone, and incremental fetch against the configured PDS.
playwright-test/conftest.py e2e-tests/playwright-tests/conftest.py
playwright-test/requirements.txt e2e-tests/playwright-tests/requirements.txt
playwright-test/run.sh e2e-tests/playwright-tests/run.sh
playwright-test/test_oauth_push.py e2e-tests/playwright-tests/test_oauth_push.py
scripts/pds-dev/README.md e2e-tests/pds-dev/README.md
scripts/pds-dev/compose.yaml e2e-tests/pds-dev/compose.yaml
scripts/pds-dev/create-account.sh e2e-tests/pds-dev/create-account.sh
scripts/pds-dev/login.sh e2e-tests/pds-dev/login.sh
scripts/pds-dev/reset.sh e2e-tests/pds-dev/reset.sh
scripts/pds-dev/run-e2e.sh e2e-tests/pds-dev/run-e2e.sh
scripts/pds-dev/setup.sh e2e-tests/pds-dev/setup.sh
scripts/pds-dev/start.sh e2e-tests/pds-dev/start.sh
scripts/pds-dev/stop.sh e2e-tests/pds-dev/stop.sh
+1 -1
scripts/remote-test/MANUAL-TEST.md e2e-tests/remote-test/MANUAL-TEST.md
··· 130 130 PDS_URL=https://YOUR-PDS-URL \ 131 131 PDS_HANDLE=YOUR-HANDLE \ 132 132 PDS_PASSWORD=your-password \ 133 - bash pds-git-remote/scripts/remote-test/run.sh 133 + bash pds-git-remote/e2e-tests/remote-test/run.sh 134 134 ```
scripts/remote-test/run-dpop.sh e2e-tests/remote-test/run-dpop.sh
scripts/remote-test/run.sh e2e-tests/remote-test/run.sh
+1 -1
tests/e2e_tests.rs
··· 1 1 //! End-to-end tests against a real local PDS. 2 2 //! 3 3 //! Gated behind the `e2e` feature flag. Requires a running PDS at 4 - //! localhost:3000 with a test account created via scripts/pds-dev/. 4 + //! localhost:3000 with a test account created via e2e-tests/pds-dev/. 5 5 //! 6 6 //! Run with: cargo test -p pds-git-remote --features e2e -- --test-threads=1 7 7 #![cfg(feature = "e2e")]
+1 -1
tests/push_tests.rs
··· 1 1 //! Integration tests for push flow logic. 2 2 //! 3 3 //! Tests the bundle-creation and state-assembly parts of push. 4 - //! Full end-to-end push tests require a running PDS (see scripts/pds-dev/). 4 + //! Full end-to-end push tests require a running PDS (see e2e-tests/pds-dev/). 5 5 6 6 use std::path::Path; 7 7 use tokio::fs;