* allure test reporting
* make reports only for the main job
* fail a test for demo
* fail a test for demo
* revert
* fail a test for demo
* revert
* deploy to allure-jswaku
* use PAT
* add pat as secret
* check if pat exists
* debug secrets issue
* remove debug steps
* debug1
* debug2
* debug3
* debug4
* set reports for all tests
* fix after ci run
* self review
---------
Co-authored-by: Sasha <118575614+weboko@users.noreply.github.com>
* add Firefox and Webkit to karma testing
* try adding install to CI
* add display var
* try container prop
* try FirefoxHeadless
* set env var differently
* apply for all configs
* use root karma config
* fix relative link in karma config
* add log
* return as before
* fix path pattern
* move karma to the root
* try moving tsconfig
* return ts config
* use container for playwright
* add FF for firefox and chrome
* use command for playwright
* add retries
* remove retries
* added workflow call for reusable workflows
* explicitly checkout js-waku
* fix wrong org
* fix input passing
* excluded unneded jobs for when caller is nwaku
* excluded check and proto as well
---------
Co-authored-by: Sasha <118575614+weboko@users.noreply.github.com>
* chore: add retry to test steps of ci
* use another action for retry
* fix version
* use master version
* test with error
* return working version
* add env var
* return node test
* merge: master
* fix: CI
* use: js script instead of shell script to run precheck and mocha
* use `console.log` instead of `debug.log` for `run-tests.js`
* chore: change `localhost` -> `127.0.0.1`
There is a change in how Node does DNS resolution in Node 18 vs
16 -- `localhost` resolves to `::1`, which is the equivalent of
`127.0.0.1` but in IPv6 instead of IPv4. The server however is
only listening on IPv4.
Reference:
https://github.com/nodejs/node/issues/40702#issuecomment-958143154
* refactor: change node version on CI from 16 to 18
