python
diff --git a/‎Tools/wasm/README.md
Lines changed: 11 additions & 0 deletions b/‎Tools/wasm/README.md
Lines changed: 11 additions & 0 deletions
diff --git a/‎Tools/wasm/emscripten/browser_test/.gitignore
Lines changed: 4 additions & 0 deletions b/‎Tools/wasm/emscripten/browser_test/.gitignore
Lines changed: 4 additions & 0 deletions
diff --git a/‎Tools/wasm/emscripten/browser_test/index.spec.ts
Lines changed: 15 additions & 0 deletions b/‎Tools/wasm/emscripten/browser_test/index.spec.ts
Lines changed: 15 additions & 0 deletions
@@ -84,6 +84,17 @@ make a node application that "embeds" the interpreter instead of acting like the
 CLI you will need to write your own alternative to `node_entry.mjs`.
 
 
+### Running tests
+
+After building, you can run the full test suite with:
+```shell
+./cross-build/wasm32-emscripten/build/python/python.sh -m test -uall
+```
+You can run the browser smoke test with:
+```shell
+./Tools/wasm/emscripten/browser_test/run_test.sh
+```
+
 ### The Web Example
 
 When building for Emscripten, the web example will be built automatically. It
 
@@ -0,0 +1,4 @@
+node_modules
+test-results
+playwright-report
+test_log.txt
@@ -0,0 +1,15 @@
+import { test, expect } from '@playwright/test';
+
+test('has title', async ({ page }) => {
+  await page.goto('/');
+
+  await expect(page).toHaveTitle("Emscripten PyRepl Example");
+  const xterm = await page.locator('css=#terminal');
+  await expect(xterm).toHaveText(/Python.*on emscripten.*Type.*for more information/);
+  const xtermInput = await page.getByRole('textbox');
+  await xtermInput.pressSequentially(`def f():\nprint("hello", "emscripten repl!")\n\n`);
+  await xtermInput.pressSequentially(`f()\n`);
+  await expect(xterm).toHaveText(/hello emscripten repl!/);
+
+});
+