chore: rename mocha-runner (#10984)

This commit is contained in:
jrandolf 2023-09-22 01:57:18 -07:00 committed by GitHub
parent 18ba47e043
commit d124c83dad
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
15 changed files with 11 additions and 11 deletions

View File

@ -239,7 +239,7 @@ module.exports = {
{
files: [
'packages/puppeteer-core/src/**/*.test.ts',
'tools/mochaRunner/src/test.ts',
'tools/mocha-runner/src/test.ts',
],
rules: {
// With the Node.js test runner, `describe` and `it` are technically

View File

@ -41,7 +41,7 @@ jobs:
- 'docker/**'
- 'test/**'
- 'test-d/**'
- 'tools/mochaRunner/**'
- 'tools/mocha-runner/**'
- '.mocharc.cjs'
- 'tools/doctest/**'
website:

View File

@ -107,7 +107,7 @@ Puppeteer uses a custom test runner on top of Mocha that consults the
[TestExpectations.json](https://github.com/puppeteer/puppeteer/blob/main/test/TestExpectations.json)
to see if a given test result is expected or not. See more info about the test
runner in
[`tools/mochaRunner`](https://github.com/puppeteer/puppeteer/tree/main/tools/mochaRunner).
[`tools/mocha-runner`](https://github.com/puppeteer/puppeteer/tree/main/tools/mocha-runner).
### Unit tests
@ -155,7 +155,7 @@ The following is a description of the primary folders in Puppeteer:
- `test-d` contains type tests using
[`tsd`](https://github.com/SamVerschueren/tsd).
- `tools` contains miscellaneous scripts that are used in building and etc.
- `tools/mochaRunner` - contains the source code for our test runner.
- `tools/mocha-runner` - contains the source code for our test runner.
## API guidelines
@ -248,7 +248,7 @@ for details.
If a test is expected to fail on certain configurations or became flaky, update
[TestExpectations.json](https://github.com/puppeteer/puppeteer/blob/main/test/TestExpectations.json)
to reflect that. See more info about TestExpectations.json in
[`tools/mochaRunner`](https://github.com/puppeteer/puppeteer/tree/main/tools/mochaRunner).
[`tools/mocha-runner`](https://github.com/puppeteer/puppeteer/tree/main/tools/mocha-runner).
## API Coverage

View File

@ -110,7 +110,7 @@
]
},
"test": {
"command": "cross-env PUPPETEER_DEFERRED_PROMISE_DEBUG_TIMEOUT=20000 node tools/mochaRunner/lib/main.js --min-tests 1003",
"command": "cross-env PUPPETEER_DEFERRED_PROMISE_DEBUG_TIMEOUT=20000 node tools/mocha-runner/lib/main.js --min-tests 1003",
"dependencies": [
"./test:build"
]

View File

@ -25,7 +25,7 @@ The best place to look is an existing test to see how they use the helpers.
## Skipping tests in specific conditions
To skip tests edit the [TestExpectations](https://github.com/puppeteer/puppeteer/blob/main/test/TestExpectations.json) file. See [test runner documentation](https://github.com/puppeteer/puppeteer/tree/main/tools/mochaRunner) for more details.
To skip tests edit the [TestExpectations](https://github.com/puppeteer/puppeteer/blob/main/test/TestExpectations.json) file. See [test runner documentation](https://github.com/puppeteer/puppeteer/tree/main/tools/mocha-runner) for more details.
## Running tests

View File

@ -15,7 +15,7 @@
"../packages/testserver:build"
],
"files": [
"../tools/mochaRunner/**",
"../tools/mocha-runner/**",
"src/**"
],
"output": [

View File

@ -7,5 +7,5 @@
"rootDir": "src"
},
"include": ["src"],
"references": [{"path": "../tools/mochaRunner/tsconfig.json"}]
"references": [{"path": "../tools/mocha-runner/tsconfig.json"}]
}

View File

@ -6,7 +6,7 @@ It uses `/test/TestSuites.json` and `/test/TestExpectations.json` files to run m
## Running tests for Mocha Runner itself.
```bash
npm run build && npx c8 node tools/mochaRunner/lib/test.js
npm run build && npx c8 node tools/mocha-runner/lib/test.js
```
## Running tests using Mocha Runner

View File

@ -59,7 +59,7 @@ export interface MochaResults {
pending: MochaTestResult[];
passes: MochaTestResult[];
failures: MochaTestResult[];
// Added by mochaRunner.
// Added by mocha-runner.
updates?: RecommendedExpectation[];
parameters?: string[];
platform?: string;