Add lldb debug integration tests config, upgrade mocha to prevent chi…

…ld process being spawned (realm#4085)

* Add lldb debug integration tests config, upgrade mocha to prevent child process being spawned

* Add .mocharc.json to use ts-node

.vscode/launch.json

@@ -89,6 +89,24 @@
  ],
  "cwd": "${workspaceFolder}/tests"
  },
+ {
+ "type": "lldb",
+ "request": "launch",
+ "name": "LLDB Debug Integration Tests",
+ "program": "node",
+ "args": [
+ "--expose_gc",
+ "node_modules/mocha/bin/mocha",
+ "--require",
+ "ts-node/register/transpile-only",
+ "--require",
+ "src/utils/inject-node-globals.ts",
+ "src/index.ts",
+ "--grep",
+ "${input:integrationTestFilter}"
+ ],
+ "cwd": "${workspaceFolder}/integration-tests/tests"
+ }
  ],
  "compounds": [
  {
@@ -112,6 +130,12 @@
  "type": "promptString",
  "default": ".",
  "description": "Filtering used to limit what tests are run"
+ },
+ {
+ "id": "integrationTestFilter",
+ "type": "promptString",
+ "default": "",
+ "description": "Filtering used to limit what tests are run"
  }
  ]
 }

integration-tests/README.md

@@ -71,6 +71,12 @@ When running the environments individually the test suite's TypeScript is not au
 npm run build:watch --prefix tests
 ```
 
+## Running tests with a C++ debugger attached
+
+In order to debug the tests with `lldb` attached to debug C++, you can use the VS Code launch configuration `LLDB Debug Integration Tests`.
+
+This bypasses the usual startup script (as this spawns a child process for the tests, which stops `lldb` working), so you need to have the app importer running separately when doing this: `npm run app-importer` from the `integration-tests/tests` directory.
+
 ---
 
 ## Maintaining the tests

integration-tests/tests/.mocharc.json

@@ -0,0 +1,4 @@
+{
+ "extension": ["ts"],
+ "require": ["ts-node/register/transpile-only", "src/utils/inject-node-globals.ts"]
+}