status-im
/
js-waku
mirror of https://github.com/status-im/js-waku.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
js-waku/packages/tests
History
Danish Arora 6ce898d771
feat: enable event emission for peer discovery/connection in ConnectionManager (#1438) 
* disable libp2p autodial

* improve logs for peer-exchange

* add a function to fetch discovered and connected peers by discovery

* connection-manager: introduce event emissions by discovery

* write a spec test for events

* minor code improvement for peer-exchange

* rm: comment

* rename peer event result interface

* switch to using libp2p EventEmitter

* rename variables for readability

* reset peer-exchange spec file

* address review

* test: minor refactor

* fix: failing test

* increase peer IDs to test against for attemptDial

* improve structuring
 		2023-07-26 22:51:55 +05:30
..
src chore: new eslint rules (#1416) 2023-07-24 16:04:24 +05:30
tests feat: enable event emission for peer discovery/connection in ConnectionManager (#1438) 2023-07-26 22:51:55 +05:30
.eslintrc.cjs feat: use nwaku/go-waku docker images instead of building binaries (#1259) 2023-04-17 10:29:36 +05:30
.mocharc.json chore: remove usage of jsdom 2023-02-10 19:44:59 +11:00
README.md feat: use nwaku/go-waku docker images instead of building binaries (#1259) 2023-04-17 10:29:36 +05:30
package.json chore(deps)(deps-dev): bump @typescript-eslint/parser (#1436) 2023-07-25 22:41:55 +05:30
tsconfig.dev.json chore: merge tsconfig 2022-12-02 15:54:30 +11:00
tsconfig.json feat: use nwaku/go-waku docker images instead of building binaries (#1259) 2023-04-17 10:29:36 +05:30

README.md

Description

This package contains tests for the js-waku library.

Pre-requisites

Some of the tests from this package require a running nwaku or go-waku node. These nodes are setup to be run in a docker container. Therefore, you need to have docker installed on your machine to run the tests.

Running interop tests

  • The tests by default run against an nwaku node with the image name specified in nwaku.ts and packages/tests/package.json. The tests can be run against a different image by setting the environment variable WAKUNODE_IMAGE to the desired image.

  • The tests can be run against a go-waku node by setting the environment variable WAKUNODE_IMAGE to the desired go-waku image.

    • Whatever WAKUNODE_IMAGE is set to, the tests will run against that image. If the image is not available locally, the tests will pull the image from the docker hub. You can run the tests by running the following command:

      WAKUNODE_IMAGE=explicit-image-name npm run test:node

      Or against the default docker image by running:

      npm run test:node

  • You can also run the tests against a local nwaku or go-waku node by setting the environment variable WAKUNODE_IMAGE to the name of the image. The tests will then run against the local image.

    • For example, to run the tests against a local checkout of nwaku or go-waku, build the image first manually. You can build the image by running the following command:

      docker build path-to-dockerfile -t image-name

      Then, you can run the tests by running the following command:

      WAKUNODE_IMAGE=image-name npm run test:node