[Epic] Comprehensive Dev Testing

[fryorcraken]

Epic label: E:Comprehensive dev testing

Summary

Epic to track testing effort (as done by Waku engineers) to ensure high quality software and stability.

This epic can be seen as a laundry that each client should review and extract action items if application to the client.

This excludes end-to-end testing effort (#34).

Acceptance Criteria

• CI is stable with minimum false negative (no flacky CI)
• Target environments are included in the CI (e.g. Linux/Mac, browser/node, etc)
  • Cover Several Environments As Part of Testing js-waku#52
• Test coverage is tracked and on target (if applicable, target to be set per client)
  • Improve Test Coverage go-waku#620
• Performance, low level system profiling, static analysis are setup and run as part of CI or release.
  • Memory profiling
  • Race condition analysis
  • Code maintainability
  • Static analysis

Tasks

• js-waku: Setup code climate and maintain score of A js-waku#1589
• js-waku: feat: setup size-limit report and define size budget js-waku#1435
• js-waku: Optimize js-waku for the Browser js-waku#337
• js-waku: feat: setup test coverage js-waku#1595
• js-waku: feat: configure playwright to test other examples based on env var js-waku#1597