You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+35-35Lines changed: 35 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,22 @@
1
1
## 2.0.3
2
2
3
-
* fix: subprocess processing should not stop when unhandled rejection occurs ([#173](https://github.com/yandex/mocha-parallel-tests/issues/173))
4
-
* fix: subprocess processing should not stop when uncaught exception occurs ([#172](https://github.com/yandex/mocha-parallel-tests/issues/172))
5
-
* added a [list of limitations](https://github.com/yandex/mocha-parallel-tests/wiki/Limitations) that you can hit when you launch your tests with `mocha-parallel-tests`
3
+
* fix: subprocess processing should not stop when unhandled rejection occurs ([#173](https://github.com/mocha-parallel/mocha-parallel-tests/issues/173))
4
+
* fix: subprocess processing should not stop when uncaught exception occurs ([#172](https://github.com/mocha-parallel/mocha-parallel-tests/issues/172))
5
+
* added a [list of limitations](https://github.com/mocha-parallel/mocha-parallel-tests/wiki/Limitations) that you can hit when you launch your tests with `mocha-parallel-tests`
6
6
7
7
## 2.0.2
8
8
9
-
* fix: subprocess stderr is not shown if the subprocess crashes before sending the "start" event ([#158](https://github.com/yandex/mocha-parallel-tests/issues/158))
10
-
* fix: `--retries` and `--bail` option conflict with each other causing `mohcha-parallel-tests` own assertion error ([#163](https://github.com/yandex/mocha-parallel-tests/issues/163))
9
+
* fix: subprocess stderr is not shown if the subprocess crashes before sending the "start" event ([#158](https://github.com/mocha-parallel/mocha-parallel-tests/issues/158))
10
+
* fix: `--retries` and `--bail` option conflict with each other causing `mohcha-parallel-tests` own assertion error ([#163](https://github.com/mocha-parallel/mocha-parallel-tests/issues/163))
11
11
12
12
## 2.0.1
13
13
14
-
* fix: reporter doesn't show anything until all tests are finished ([#145](https://github.com/yandex/mocha-parallel-tests/issues/145))
15
-
* fix: wrong assertion error when subprocess crashes before sending test results ([#147](https://github.com/yandex/mocha-parallel-tests/issues/147))
16
-
* fix: `--exit` option was not working as expected ([#146](https://github.com/yandex/mocha-parallel-tests/issues/146))
17
-
* fix: wrong assertion error when `--retries` option is used and all retries fail ([#143](https://github.com/yandex/mocha-parallel-tests/issues/143))
18
-
* fix: events order is not following `mocha` style. This fixes `mochawesome` reporter behaviour ([#113](https://github.com/yandex/mocha-parallel-tests/issues/113))
19
-
*`mocha-allure-reporter` is supported ([#80](https://github.com/yandex/mocha-parallel-tests/issues/80))
14
+
* fix: reporter doesn't show anything until all tests are finished ([#145](https://github.com/mocha-parallel/mocha-parallel-tests/issues/145))
15
+
* fix: wrong assertion error when subprocess crashes before sending test results ([#147](https://github.com/mocha-parallel/mocha-parallel-tests/issues/147))
16
+
* fix: `--exit` option was not working as expected ([#146](https://github.com/mocha-parallel/mocha-parallel-tests/issues/146))
17
+
* fix: wrong assertion error when `--retries` option is used and all retries fail ([#143](https://github.com/mocha-parallel/mocha-parallel-tests/issues/143))
18
+
* fix: events order is not following `mocha` style. This fixes `mochawesome` reporter behaviour ([#113](https://github.com/mocha-parallel/mocha-parallel-tests/issues/113))
19
+
*`mocha-allure-reporter` is supported ([#80](https://github.com/mocha-parallel/mocha-parallel-tests/issues/80))
20
20
21
21
## 2.0.0
22
22
@@ -37,85 +37,85 @@ Some of the main changes are:
37
37
* new: `mocha-parallel-tests` install should work fine on windows
38
38
* new: TypeScript definitions are now provided in package.json
39
39
40
-
Read more about new release here: https://github.com/yandex/mocha-parallel-tests/wiki/v2-release-notes
40
+
Read more about new release here: https://github.com/mocha-parallel/mocha-parallel-tests/wiki/v2-release-notes
41
41
42
42
## 1.2.10
43
43
44
-
* fix: support `--no-timeouts` option ([#120](https://github.com/yandex/mocha-parallel-tests/issues/120))
44
+
* fix: support `--no-timeouts` option ([#120](https://github.com/mocha-parallel/mocha-parallel-tests/issues/120))
45
45
46
46
## 1.2.9
47
47
48
-
* fix: support only latest (3.x) `mocha` versions ([#98](https://github.com/yandex/mocha-parallel-tests/issues/98))
49
-
* fix: support `reporter.done()` callback for all external reporters (`mochawesome` for example) in both CLI and node.js API ([#113](https://github.com/yandex/mocha-parallel-tests/issues/113))
48
+
* fix: support only latest (3.x) `mocha` versions ([#98](https://github.com/mocha-parallel/mocha-parallel-tests/issues/98))
49
+
* fix: support `reporter.done()` callback for all external reporters (`mochawesome` for example) in both CLI and node.js API ([#113](https://github.com/mocha-parallel/mocha-parallel-tests/issues/113))
50
50
51
51
## 1.2.8
52
52
53
-
* fix: do not fail if no target is set and `--recursive` option is used ([#94](https://github.com/yandex/mocha-parallel-tests/issues/94))
53
+
* fix: do not fail if no target is set and `--recursive` option is used ([#94](https://github.com/mocha-parallel/mocha-parallel-tests/issues/94))
54
54
55
55
## 1.2.7
56
56
57
-
* fix: add support for `xdescribe`, `xcontext`, `xspecify`, `xit` and `it.skip` ([#102](https://github.com/yandex/mocha-parallel-tests/issues/102))
57
+
* fix: add support for `xdescribe`, `xcontext`, `xspecify`, `xit` and `it.skip` ([#102](https://github.com/mocha-parallel/mocha-parallel-tests/issues/102))
58
58
* most of packages dependencies upgrade (minor changes)
59
59
60
60
## 1.2.6
61
61
62
-
* fix: tests with binary dependencies can now be used with `mocha-parallel-tests` ([#100](https://github.com/yandex/mocha-parallel-tests/issues/100))
62
+
* fix: tests with binary dependencies can now be used with `mocha-parallel-tests` ([#100](https://github.com/mocha-parallel/mocha-parallel-tests/issues/100))
63
63
64
64
## 1.2.5
65
65
66
-
* fix: if file contains multiple `describe()` sections in it, one of it fails and `mocha-parallel-tests` is executed with `--retry` option, only this failed section is re-executed ([#77](https://github.com/yandex/mocha-parallel-tests/issues/77))
66
+
* fix: if file contains multiple `describe()` sections in it, one of it fails and `mocha-parallel-tests` is executed with `--retry` option, only this failed section is re-executed ([#77](https://github.com/mocha-parallel/mocha-parallel-tests/issues/77))
67
67
68
68
## 1.2.4
69
69
70
-
* fix: `--no-exit` CLI option is supported ([#85](https://github.com/yandex/mocha-parallel-tests/issues/85))
70
+
* fix: `--no-exit` CLI option is supported ([#85](https://github.com/mocha-parallel/mocha-parallel-tests/issues/85))
71
71
72
72
## 1.2.3
73
73
74
-
* fix: pwd-based reporters (located somewhere inside your repo) are supported ([#75](https://github.com/yandex/mocha-parallel-tests/issues/75))
75
-
* fix: `tap` and other reporters which use mocha's `runner` object are supported ([#78](https://github.com/yandex/mocha-parallel-tests/issues/78))
* fix: pwd-based reporters (located somewhere inside your repo) are supported ([#75](https://github.com/mocha-parallel/mocha-parallel-tests/issues/75))
75
+
* fix: `tap` and other reporters which use mocha's `runner` object are supported ([#78](https://github.com/mocha-parallel/mocha-parallel-tests/issues/78))
* fix: `selenium-webdriver` issue with number of tests is fixed ([#69](https://github.com/yandex/mocha-parallel-tests/issues/69)). Currently all `selenium-webdriver` tests should work as expected.
80
+
* fix: `selenium-webdriver` issue with number of tests is fixed ([#69](https://github.com/mocha-parallel/mocha-parallel-tests/issues/69)). Currently all `selenium-webdriver` tests should work as expected.
81
81
82
82
## 1.2.1
83
83
84
-
* fix: `--require`'d files are working as expected together with `--compilers` option ([#63](https://github.com/yandex/mocha-parallel-tests/issues/63))
84
+
* fix: `--require`'d files are working as expected together with `--compilers` option ([#63](https://github.com/mocha-parallel/mocha-parallel-tests/issues/63))
85
85
86
86
## 1.2.0
87
87
88
88
***new**: using mocha-parallel-tests programmatically is now supported. You can also pass own mocha-parallel-tests options by calling `setOwnOptions({maxParallel, retry})` method of mocha-parallel-tests instance. You should call it before `run()`.
89
89
90
90
## 1.1.x
91
91
92
-
***breaking change**: `mocha` is now in peerDependencies part of `mocha-parallel-tests` which means that you need to add both `mocha` and `mocha-parallel-tests` in your project's package.json. This also means that you can run both of your tests: written for mocha@2.x and mocha@3.x ([#55](https://github.com/yandex/mocha-parallel-tests/issues/55))
93
-
* fix: support for only() and skip() helpers ([#59](https://github.com/yandex/mocha-parallel-tests/issues/59))
92
+
***breaking change**: `mocha` is now in peerDependencies part of `mocha-parallel-tests` which means that you need to add both `mocha` and `mocha-parallel-tests` in your project's package.json. This also means that you can run both of your tests: written for mocha@2.x and mocha@3.x ([#55](https://github.com/mocha-parallel/mocha-parallel-tests/issues/55))
93
+
* fix: support for only() and skip() helpers ([#59](https://github.com/mocha-parallel/mocha-parallel-tests/issues/59))
94
94
* fix: main package file now refers to CommonJS file, not ES6 module.
95
95
96
96
Version number is 1.1.0 because first `mocha-parallel-tests` releases had 1.0.x versioning scheme.
97
97
98
98
## 0.5.x
99
99
100
100
***new**: mutiple test suites (describe) inside one file run in parallel
101
-
* fix: support mocha `--compilers` option ([#53](https://github.com/yandex/mocha-parallel-tests/issues/53)). `0.4.x` lacked support for JavaScript files.
101
+
* fix: support mocha `--compilers` option ([#53](https://github.com/mocha-parallel/mocha-parallel-tests/issues/53)). `0.4.x` lacked support for JavaScript files.
102
102
* fix: support mocha `--require` option
103
-
* fix: support [mocha.opts](https://mochajs.org/#mochaopts) config file ([#44](https://github.com/yandex/mocha-parallel-tests/issues/44))
104
-
* fix: global hooks stored inside separate files are now executed if target is directory ([#41](https://github.com/yandex/mocha-parallel-tests/issues/41))
105
-
* fix: global hooks stored inside separate files are now executed ([#39](https://github.com/yandex/mocha-parallel-tests/issues/39))
103
+
* fix: support [mocha.opts](https://mochajs.org/#mochaopts) config file ([#44](https://github.com/mocha-parallel/mocha-parallel-tests/issues/44))
104
+
* fix: global hooks stored inside separate files are now executed if target is directory ([#41](https://github.com/mocha-parallel/mocha-parallel-tests/issues/41))
105
+
* fix: global hooks stored inside separate files are now executed ([#39](https://github.com/mocha-parallel/mocha-parallel-tests/issues/39))
106
106
107
107
## 0.4.x
108
108
109
109
***new**: support for mocha `--compilers` option introduced
110
-
* fix: tests using `--max-parallel=1` run without errors ([#34](https://github.com/yandex/mocha-parallel-tests/issues/34))
111
-
* fix: reporters with own options like `xunit` don't produce errors now ([#31](https://github.com/yandex/mocha-parallel-tests/issues/31))
110
+
* fix: tests using `--max-parallel=1` run without errors ([#34](https://github.com/mocha-parallel/mocha-parallel-tests/issues/34))
111
+
* fix: reporters with own options like `xunit` don't produce errors now ([#31](https://github.com/mocha-parallel/mocha-parallel-tests/issues/31))
112
112
* fix: `--retry` option is now working for mocha test hooks (before/after/etc)
113
113
*`mocha-parallel-tests` code is now ES2015-compatible
114
114
115
115
## 0.3.x
116
116
117
-
* fix: runner displays right tests execution time now ([#24](https://github.com/yandex/mocha-parallel-tests/issues/24))
118
-
* fix: exit codes are now the same as in original mocha runner ([#27](https://github.com/yandex/mocha-parallel-tests/issues/27))
117
+
* fix: runner displays right tests execution time now ([#24](https://github.com/mocha-parallel/mocha-parallel-tests/issues/24))
118
+
* fix: exit codes are now the same as in original mocha runner ([#27](https://github.com/mocha-parallel/mocha-parallel-tests/issues/27))
119
119
* bump `mocha` version to 2.4.5. Check its [changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md) for more info. Previous version was 2.3.4.
`mocha-parallel-tests` is a test runner for tests written with `mocha` testing framework which allows you to run them in parallel. `mocha-parallel-tests` executes **each of your test files in a separate process** while maintaining the output structure of `mocha`. Compared to the other tools which try to parallelize `mocha` tests execution, `mocha-parallel-tests` doesn't require you to write the code in a different way or use some specific APIs - just run your tests with `mocha-parallel-tests` instead of `mocha` and you will see the difference. Or if you prefer to use `mocha` programmatic API replace it with `mocha-parallel-tests` default export and you're done!
6
6
@@ -48,9 +48,9 @@ mocha.run();
48
48
49
49
## Differences with mocha
50
50
51
-
Main difference with `mocha` comes from the fact that all files are executed in separate processes and don't share the scope. This means that even global variables values that you could've used to share the data between test suites will not be reliable. There's also some specific behaviour for some of the `mocha` CLI options like `--bail`: it's just applied to each test in its process. You can see the full list of differences [here](https://github.com/yandex/mocha-parallel-tests/wiki/Differences-with-mocha).
51
+
Main difference with `mocha` comes from the fact that all files are executed in separate processes and don't share the scope. This means that even global variables values that you could've used to share the data between test suites will not be reliable. There's also some specific behaviour for some of the `mocha` CLI options like `--bail`: it's just applied to each test in its process. You can see the full list of differences [here](https://github.com/mocha-parallel/mocha-parallel-tests/wiki/Differences-with-mocha).
52
52
53
-
There's also a [list of limitations](https://github.com/yandex/mocha-parallel-tests/wiki/Limitations) that you can hit when you launch your tests with `mocha-parallel-tests`.
53
+
There's also a [list of limitations](https://github.com/mocha-parallel/mocha-parallel-tests/wiki/Limitations) that you can hit when you launch your tests with `mocha-parallel-tests`.
54
54
55
55
From the reporter perspective the main difference between tests executed with `mocha` and `mocha-parallel-tests` is another level of nesting which again comes from the fact that main process adds one more "suite" level and all tests results are merged into that:
56
56
@@ -68,4 +68,4 @@ From the reporter perspective the main difference between tests executed with `m
68
68
69
69
## Comparison with `mocha.parallel`
70
70
71
-
[mocha.parallel](https://github.com/danielstjules/mocha.parallel) is a tool which allows you to run mocha tests in parallel. While it seems pretty similar to `mocha-parallel-tests` there's a massive difference between them. Check [this page](https://github.com/yandex/mocha-parallel-tests/wiki/Comparison-with-mocha.parallel) for a full comparison.
71
+
[mocha.parallel](https://github.com/danielstjules/mocha.parallel) is a tool which allows you to run mocha tests in parallel. While it seems pretty similar to `mocha-parallel-tests` there's a massive difference between them. Check [this page](https://github.com/mocha-parallel/mocha-parallel-tests/wiki/Comparison-with-mocha.parallel) for a full comparison.
0 commit comments