chore: CI should have human readable logs + json for reporting

[danisharora099]

Problem / Description

We recently switched to a JSON reporter for our tests.
This created a side-effect where logs were now being printed in JSON, instead of human-readable format (spec)

Solution

Use multi-reporter:

• use spec (human readable) for logs (stdout)
• use JSON for report

---

Checklist

• Code changes are covered by unit tests.
• Code changes are covered by e2e tests, if applicable.
• Dogfooding has been performed, if feasible.
• A test version has been published, if required.
• All CI checks pass successfully.

[github-actions]

size-limit report 📦

Path	Size	Loading time (3g)	Running time (snapdragon)	Total time
Waku node	84.74 KB (0%)	1.7 s (0%)	11.3 s (-20.66% 🔽)	13 s
Waku Simple Light Node	135.73 KB (0%)	2.8 s (0%)	17 s (-6.26% 🔽)	19.7 s
ECIES encryption	22.73 KB (0%)	455 ms (0%)	5.4 s (+10.63% 🔺)	5.8 s
Symmetric encryption	22.23 KB (0%)	445 ms (0%)	4.4 s (-19.37% 🔽)	4.9 s
DNS discovery	70.8 KB (0%)	1.5 s (0%)	11.9 s (-5.18% 🔽)	13.3 s
Peer Exchange discovery	71.8 KB (0%)	1.5 s (0%)	8 s (-27.9% 🔽)	9.5 s
Local Peer Cache Discovery	65.39 KB (0%)	1.4 s (0%)	11.2 s (-20.73% 🔽)	12.5 s
Privacy preserving protocols	76.52 KB (0%)	1.6 s (0%)	11.7 s (-1.37% 🔽)	13.3 s
Waku Filter	78.11 KB (0%)	1.6 s (0%)	11.6 s (+9.99% 🔺)	13.2 s
Waku LightPush	75.6 KB (0%)	1.6 s (0%)	13.5 s (+15.08% 🔺)	15 s
History retrieval protocols	75.78 KB (0%)	1.6 s (0%)	11.7 s (+3.78% 🔺)	13.2 s
Deterministic Message Hashing	7.32 KB (0%)	147 ms (0%)	2.1 s (-0.74% 🔽)	2.2 s

[weboko]

why do we create and save reports? Is it to be displayed in the pipeline later?
I know before we were doing so to push allure reports but why this one is done?

[danisharora099]

similar situation, we generate the reports and use GH UI to display it

[weboko]

seems good but test reporting has failed

[danisharora099]

Moving to draft for now based on:

There's a bigger problem with using this test reporter:

This reporter expects JSON reporting; this leads us to generate reports in both spec/human-readable (for CI logs) and JSON (for the above test reporter)
- `mocha-multi-reporters` has the ability to generate reports in multiple formats, but that leaves us with JSON reports also being logged in the CI, along with spec

There is no way to disable logging for one reporter through Mocha.

So:
- either we run our tests twice, once through JSON and once through spec (not ideal)
- implement a custom reporter
- use some other reporter/testing framework


Are we considering going back to Allure? This will help with making a decision on how to best move forward.

If no, we can explore implementing a custom reporter, or infact switching to something like Jest or Vitest. They seem to handle reporting better and could give us the flexibility we need for both readable output and JSON reports without the current conflicts

https://discord.com/channels/1110799176264056863/1333438262013989018/1334858240235929632

[danisharora099]

redundant based on allure merge back