tests: integration and mocking test for fastqueue playwright, setup CI on github ctions

.github/workflows/ci.yml

@@ -0,0 +1,22 @@
+name: integration-tests
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node-version: [20, 22]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: npm
+      - run: npm ci
+      - run: npm test

README.md

@@ -1,5 +1,7 @@
 ### fastqueue-playwright
 
+[![integration-tests](https://github.com/sodrooome/fastqueue-playwright/actions/workflows/ci.yml/badge.svg)](https://github.com/sodrooome/fastqueue-playwright/actions/workflows/ci.yml)
+
 Internal tooling that's being developed at MauKerja Malaysia, which is used for distributed workload scheduling across different teams to orchestrate massive Playwright end-to-end UI automation tests for MauKerja Malaysia/Ricebowl Malaysia/internal dashboard platforms and such
 
 Decided to make it as an open-source with limited constraints after a round of discussion so it won't be disclosed all the critical functionality
@@ -129,6 +131,19 @@ Once you run the command, it will discover the test files and then the workers w
 All batches were completed
 ```
 
+**Run the tests**
+
+If you want to run the integration tests locally, you can execute the command:
+
+```bash
+npm test
+
+# or for watch mode
+npm run test:watch
+```
+
+Afterwards it will be run over 34 different test cases which are compromised of unit test for individual modules, integration tests around `discovery.ts`, `worker.ts` and also orchestrator test
+
 ### Integrating with Github Actions
 
 If you want to use this *messed up* codebase in your actual Github Actions workflow, just drop a few things on your `.yml` file in a particular repo and it's good to go. For example you may use this necessary setup: