whatsapp-web.js

mirror of https://github.com/cheveguerra/whatsapp-web.js.git synced 2026-04-18 03:29:14 +00:00

Files

Pedro S. Lopez 2718c1328c fix compatibility issues with WhatsApp Web 2.2208.7 (#1311 )

* fix compatiblity issues with v2.2208.7

* remove expclusive test

2022-03-09 00:54:57 -04:00

structures

feat: Multi-device support (#889 )

2022-02-27 18:51:08 -04:00

client.js

fix compatibility issues with WhatsApp Web 2.2208.7 (#1311 )

2022-03-09 00:54:57 -04:00

helper.js

update tests to work with authStrategies

2022-02-27 22:18:54 -04:00

README.md

feat: Multi-device support (#889 )

2022-02-27 18:51:08 -04: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_SESSION: A JSON-formatted string with legacy auth session details. Must include WABrowserId, WASecretBundle, WAToken1 and WAToken2.
WWEBJS_TEST_SESSION_PATH: Path to a JSON file that contains the legacy auth session details. Must include WABrowserId, WASecretBundle, WAToken1 and WAToken2.
WWEBJS_TEST_CLIENT_ID: clientId to use for local file based authentication.
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.

You must set WWEBJS_TEST_REMOTE_ID and either WWEBJS_TEST_SESSION, WWEBJS_TEST_SESSION_PATH or WWEBJS_TEST_CLIENT_ID for the tests to run properly.

Multidevice

Some of the tested functionality depends on whether the account has multidevice enabled or not. If you are using multidevice, you should set WWEBJS_TEST_MD=1.