Skip to content

Commit 8c97bc5

Browse files
committed
adjust
1 parent a35777c commit 8c97bc5

File tree

2 files changed

+7
-2
lines changed

2 files changed

+7
-2
lines changed

.github/workflows/ci.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,7 @@ jobs:
5858
php -S localhost:8000 -t tests/Integration/Fixtures/public &
5959
chromedriver --port=9515 &
6060
chromedriver --port=9516 &
61+
chromedriver --port=9517 &
6162
sleep 2
6263
6364
- name: Run integration tests

README.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,10 +30,12 @@ composer require --dev brianium/paratest
3030

3131
### 2. Start ChromeDriver instances
3232

33-
You need one ChromeDriver instance per parallel process. By default the package uses ports starting from `9515`:
33+
You need one ChromeDriver instance per parallel process. By default, the package uses ports starting from `9515`. I recommend starting a few more instances than you think you need, as ParaTest's token assignment can be unpredictable depending on your environment:
3434
```bash
3535
chromedriver --port=9515 &
3636
chromedriver --port=9516 &
37+
chromedriver --port=9517 &
38+
chromedriver --port=9518 &
3739
```
3840

3941
### 3. Run your tests
@@ -101,13 +103,15 @@ abstract class DuskTestCase extends ParallelTestCase
101103
run: |
102104
chromedriver --port=9515 &
103105
chromedriver --port=9516 &
106+
chromedriver --port=9517 &
107+
chromedriver --port=9518 &
104108
sleep 2
105109
106110
- name: Run Dusk tests
107111
run: php artisan dusk:parallel --processes=2
108112
```
109113
110-
Both ChromeDriver instances run on the same runner, so there is no additional CI cost compared to running Dusk sequentially.
114+
All ChromeDriver instances run on the same runner, so there is no additional CI cost compared to running Dusk sequentially.
111115
112116
## How it works
113117

0 commit comments

Comments
 (0)