Minor improvements

Author: ianthomas23

test/conftest_lite.py

@@ -28,8 +28,8 @@
 
 # Files in the JupyterLite drive that a command's stdout and stderr are written to.
 # Terminal path /drive/<name> corresponds to JupyterLite contents path <name>.
-STDOUT_FILE = "lite_stdout.txt"
-STDERR_FILE = "lite_stderr.txt"
+STDOUT_FILE = "stdout.txt"
+STDERR_FILE = "stderr.txt"
 
 # Command line that writes the exit code of the previous command line and the shell's cwd to the
 # terminal, as lines such as '?=0' and 'PWD=/drive'.

wasm/README.md

@@ -121,23 +121,6 @@ GIT2CPP_TEST_WASM=cockle pytest -v test_git.py::test_version
 GIT2CPP_TEST_WASM=lite pytest -v test_git.py::test_version
 ```
 
-### Watching the tests in a browser
-
-The tests use [pytest-playwright](https://playwright.dev/python/docs/test-runners) so its command
-line options can be used to see what is happening in the browser, for both `cockle` and `lite`:
-
-- `--headed` shows the browser window, and `--slowmo <ms>` slows down each browser operation.
-- `PWDEBUG=1` opens the Playwright Inspector to step through browser operations (use with `-s`).
-- `--tracing on` (or `retain-on-failure`) records a trace which can be viewed using
-  `playwright show-trace test-results/<test-name>/trace.zip`.
-- `--video on` (or `retain-on-failure`) records a video of each test in `test-results`.
-
-For example:
-
-```bash
-GIT2CPP_TEST_WASM=lite pytest -v --headed --slowmo 100 test_git.py::test_version
-```
-
 ### Manually running the test servers
 
 If wasm tests are failing it can be helpful to run the test servers and manually run `cockle`

wasm/lite-deploy/cockle-config-in.json

@@ -10,6 +10,7 @@
     "vi": "vim"
   },
   "environment": {
+    "GIT_CORS_PROXY": "http://localhost:8881/",
     "GIT_AUTHOR_NAME": "Jane Doe",
     "GIT_AUTHOR_EMAIL": "jane.doe@blabla.com",
     "GIT_COMMITTER_NAME": "Jane Doe",