mirror of
https://github.com/cheveguerra/whatsapp-web.js.git
synced 2026-04-18 11:39:14 +00:00
* Fix get order. * Fix types. * Add set picture for profile and for groups. * Fix bug. * Fix * Fix types * Fix eslint * Add send reaction feature. * Add send reaction feature. * Add set picture for profile and for groups. * Add send reaction feature. * Add send reaction feature. * Add send reaction feature. * Add send reaction feature. * Add send reaction feature. * Add send reaction feature. * Update src/structures/Reaction.js Co-authored-by: Noah van der Aa <ndvdaa@gmail.com> * Bug fixes. * Bug fixes. * Bug fixes. * Fix * Fix * Fix example * Fix conflict * Fix conflict * Fix conflict * Fix conflict * Fix conflict * Fix conflict * move implementation to message model Co-authored-by: Noah van der Aa <ndvdaa@gmail.com> Co-authored-by: Pedro Lopez <pedroslopez@me.com>
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 includeWABrowserId,WASecretBundle,WAToken1andWAToken2.WWEBJS_TEST_SESSION_PATH: Path to a JSON file that contains the legacy auth session details. Must includeWABrowserId,WASecretBundle,WAToken1andWAToken2.WWEBJS_TEST_CLIENT_ID:clientIdto 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.