fix: guard sort() with shuffle check so --shuffle is not silently ignored

.github/CONTRIBUTING.md

@@ -6,11 +6,12 @@ To start you need:
 
 1.  Fork the repo.
 2.  Run `npm install` to install all required libraries
-3.  Do the changes.
-4.  Add/Update Test (if possible)
-5.  Update documentation
-6.  Commit and Push to your fork
-7.  Make Pull Request
+3.  Run `npm run def`to generate types
+4.  Do the changes.
+5.  Add/Update Test (if possible)
+6.  Update documentation
+7.  Commit and Push to your fork
+8.  Make Pull Request
 
 To run codeceptjs from this repo use:
 
@@ -29,9 +30,9 @@ Depending on a type of a change you should do the following.
 
 ## Helpers
 
-Please keep in mind that CodeceptJS have **unified API** for WebDriverIO, Appium, Protractor, Nightmare, Puppeteer, TestCafe. Tests written using those helpers should be compatible at syntax level. However, some of helpers may contain unique methods. That happens. If, for instance, WebDriverIO has method XXX and Nightmare doesn't, you can implement XXX inside Nightmare using the same method signature.
+Please keep in mind that CodeceptJS have **unified API** for WebDriver, Appium, Playwright, and Puppeteer. Tests written using those helpers should be compatible at syntax level. However, some of helpers may contain unique methods. That happens. If, for instance, WebDriver has method XXX and Playwright doesn't, you can implement XXX inside Playwright using the same method signature.
 
-### Updating a WebDriverIO | Nightmare
+### Updating a WebDriver | Playwright | Puppeteer
 
 *Whenever a new method or new behavior is added it should be documented in a docblock. Valid JS-example is required! Do **not edit** `docs/helpers/`, those files are generated from docblocks in corresponding helpers! *
 
@@ -109,6 +110,16 @@ Appium tests are executed at **Semaphore CI**.
 Before applying any Core changes please raise an issue to discuss that change with core team.
 Please try to add corresponding testcase to runner or unit.
 
+## Typings
+
+Typings is generated in `typings/` directory via `jsdoc`
+
+After you updated docblock in JS file, generate typing files with next command:
+
+```
+npm run def
+```
+
 ## Documentation
 
 Documentation is stored in `/docs` directory in markdown format.
@@ -134,16 +145,6 @@ Documentation parts can be shared accross helpers. Those parts are located in `d
   }
 ```
 
-## Typings
-
-Typings is generated in `typings/` directory via `jsdoc`
-
-After you updated docblock in JS file, generate typing files with next command:
-
-```
-npm run def
-```
-
 ## Testing
 
 Whenever you implemented a feature/bugfix

.github/FUNDING.yml

@@ -0,0 +1,12 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: codeceptjs
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE.md

@@ -19,7 +19,7 @@
 * CodeceptJS version:
 * NodeJS Version:
 * Operating System:
-* puppeteer || webdriverio || protractor || testcafe version (if related)
+* puppeteer || webdriverio || playwright version (if related)
 * Configuration file:
 
 ```js

.github/PULL_REQUEST_TEMPLATE.md

@@ -4,35 +4,34 @@
 
 Applicable helpers:
 
-- [ ] WebDriver
+- [ ] Playwright
 - [ ] Puppeteer
-- [ ] Nightmare
+- [ ] WebDriver
 - [ ] REST
 - [ ] FileHelper
 - [ ] Appium
-- [ ] Protractor
-- [ ] TestCafe
-- [ ] Playwright
 
 Applicable plugins:
 
-- [ ] allure
+- [ ] aiTrace
 - [ ] autoDelay
 - [ ] autoLogin
 - [ ] customLocator
-- [ ] pauseOnFail
-- [ ] puppeteerCoverage
+- [ ] pause
+- [ ] coverage
+- [ ] heal
 - [ ] retryFailedStep
-- [ ] screenshotOnFail
+- [ ] screenshot
 - [ ] selenoid
-- [ ] stepByStepReport
-- [ ] wdio
+- [ ] stepTimeout
+- [ ] subtitles
 
 ## Type of change
 
 - [ ] :fire: Breaking changes
 - [ ] :rocket: New functionality
 - [ ] :bug: Bug fix
+- [ ] 🧹 Chore
 - [ ] :clipboard: Documentation changes/updates
 - [ ] :hotsprings: Hot fix
 - [ ] :hammer: Markdown files fix - not related to source code

.github/SHARDING_WORKFLOWS.md

@@ -0,0 +1,96 @@
+# Test Sharding Workflows
+
+This document explains the GitHub Actions workflows that demonstrate the new test sharding functionality in CodeceptJS.
+
+## Updated/Created Workflows
+
+### 1. `acceptance-tests.yml` (Updated)
+
+**Purpose**: Demonstrates sharding with acceptance tests across multiple browser configurations.
+
+**Key Features**:
+
+- Runs traditional docker-compose tests (for backward compatibility)
+- Adds new sharded acceptance tests using CodeceptJS directly
+- Tests across multiple browser configurations (Puppeteer, Playwright)
+- Uses 2x2 matrix: 2 configs × 2 shards = 4 parallel jobs
+
+**Example Output**:
+
+```
+- Sharded Tests: codecept.Puppeteer.js (Shard 1/2)
+- Sharded Tests: codecept.Puppeteer.js (Shard 2/2)
+- Sharded Tests: codecept.Playwright.js (Shard 1/2)
+- Sharded Tests: codecept.Playwright.js (Shard 2/2)
+```
+
+### 2. `sharding-demo.yml` (New)
+
+**Purpose**: Comprehensive demonstration of sharding features with larger test suite.
+
+**Key Features**:
+
+- Uses sandbox tests (2 main test files) for sharding demonstration
+- Shows basic sharding with 2-way split (`1/2`, `2/2`)
+- Demonstrates combination of `--shuffle` + `--shard` options
+- Uses `DONT_FAIL_ON_EMPTY_RUN=true` to handle cases where some shards may be empty
+
+### 3. `test.yml` (Updated)
+
+**Purpose**: Clarifies which tests support sharding.
+
+**Changes**:
+
+- Added comment explaining that runner tests are mocha-based and don't support sharding
+- Points to sharding-demo.yml for examples of CodeceptJS-based sharding
+
+## Sharding Commands Used
+
+### Basic Sharding
+
+```bash
+npx codeceptjs run --config ./codecept.js --shard 1/2
+npx codeceptjs run --config ./codecept.js --shard 2/2
+```
+
+### Combined with Other Options
+
+```bash
+npx codeceptjs run --config ./codecept.js --shuffle --shard 1/2 --verbose
+```
+
+## Test Distribution
+
+The sharding algorithm distributes tests evenly:
+
+- **38 tests across 4 shards**: ~9-10 tests per shard
+- **6 acceptance tests across 2 shards**: 3 tests per shard
+- **Uneven splits handled gracefully**: Earlier shards get extra tests when needed
+
+## Benefits Demonstrated
+
+1. **Parallel Execution**: Tests run simultaneously across multiple CI workers
+2. **No Manual Configuration**: Automatic test distribution without maintaining test lists
+3. **Load Balancing**: Even distribution ensures balanced execution times
+4. **Flexibility**: Works with any number of shards and test configurations
+5. **Integration**: Compatible with existing CodeceptJS features (`--shuffle`, `--verbose`, etc.)
+
+## CI Matrix Integration
+
+The workflows show practical CI matrix usage:
+
+```yaml
+strategy:
+  matrix:
+    config: ['codecept.Puppeteer.js', 'codecept.Playwright.js']
+    shard: ['1/2', '2/2']
+```
+
+This creates 4 parallel jobs:
+
+- Config A, Shard 1/2
+- Config A, Shard 2/2
+- Config B, Shard 1/2
+- Config B, Shard 2/2
+
+Perfect for scaling test execution across multiple machines and configurations.

.github/dependabot.yml

@@ -0,0 +1,17 @@
+version: 2
+updates:
+  # github-actions
+  - package-ecosystem: 'github-actions'
+    directory: '/'
+    schedule:
+      interval: 'weekly'
+    target-branch: '4.x'
+  # npm
+  - package-ecosystem: 'npm'
+    directory: '/'
+    schedule:
+      interval: 'weekly'
+    target-branch: '4.x'
+    ignore:
+      - dependency-name: 'escape-string-regexp'
+        versions: ['>=5.0']