eddy/whatsapp-web.js
Watch
1
0
Fork
You've already forked whatsapp-web.js
 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions
whatsapp-web.js/tests
History
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2^1 807efd502d
 chore: cleanup, ci workflows and formatting (#127064) 
* ci: setup workflows, dependabot, labeler and commit linting

* docs: update README, community files and issue templates

* chore: configure prettier, editorconfig and format codebase

* chore: restore changes lost during rebase

* docs: adjust url for new logo

* fix: align badges

* chore: resolve conflicts and re-add temp lint
2026-03-10 01:45:12 +02:00
..
structures chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
client.js chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
helper.js chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00
README.md chore: cleanup, ci workflows and formatting (#127064) 2026-03-10 01:45:12 +02:00

README.md

Running Tests

These tests require an authenticated WhatsApp Web session, as well as an additional phone that you can send messages to.

This can be configured using the following environment variables:

  • WWEBJS_TEST_CLIENT_ID: clientId to use for local file based authentication (required for authenticated tests).
  • WWEBJS_TEST_REMOTE_ID: A valid WhatsApp ID that you can send messages to, e.g. 123456789@c.us. It should be different from the ID used by the provided session (required).

You can create a .env file in the root directory with these variables. See .env.example for a template.

To run the tests:

npm test