fd59ed70fa
The test output can have occurrences of `{` that aren't the string we are looking for, eg:
```
dialer-1 | test browser
dialer-1 | [JavaScript Error: "Clear-Site-Data header found. Unknown value “"cache"”." {file: "http://127.0.0.1:34451/" line: 0}]
dialer-1 | [JavaScript Error: "Clear-Site-Data header forced the clean up of “cookies” data." {file: "http://127.0.0.1:34451/" line: 0}]
dialer-1 | [JavaScript Error: "Clear-Site-Data header forced the clean up of “storage” data." {file: "http://127.0.0.1:34451/" line: 0}]
```
These fail to parse so improve the results parsing by:
1. Try parsing every instance of `{...}` in the output, not just the first
2. Test the output for the `handshakePlusOneRTTMillis` and `pingRTTMilllis` keys
|
||
|---|---|---|
| .github | ||
| hole-punch-interop | ||
| perf | ||
| transport-interop | ||
| .gitignore | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| README.md | ||
| ROADMAP.md | ||
README.md
Interoperability/end to end test-plans & performance benchmarking for libp2p
This repository contains:
- interoperability tests for libp2p's transport layers modules across different implementations and versions
- components to run performance benchmarks for different libp2p implementations
Transport Interop
Specs
Please see our first specification for interoperability tests between transports, multiplexers, and secure channels here: Transport Interoperability Test Specs
More specs to come soon!
History
These test-plans historically used Testground. To read why we're now using docker compose instead please see: Why we're moving away from Testground
Performance Benchmarking
Please see the benchmarking README.
Roadmap
Our roadmap for test-plans can be found here: https://github.com/libp2p/test-plans/blob/master/ROADMAP.md
It represents current projects the test-plans maintainers are focused on and provides an estimation of completion targets. It is complementary to those of go-libp2p, rust-libp2p, js-libp2p, and the overarching libp2p project roadmap.
License
Dual-licensed: MIT, Apache Software License v2, by way of the Permissive License Stack.