frontier-cmp

README

Frontier cmp

Tool that compares the responses of two Frontier servers and shows the diffs. Useful for checking for regressions.

Install

Compile the frontier-cmp binary:

go install ./tools/frontier-cmp

Usage

frontier-cmp can be run in two modes:

• Crawling: start with a set of paths (defined in init_paths.go) and then uses _links to find new paths.
• ELB access log: send requests found in a provided ELB access log.

Crawling mode

To run in crawling mode specify a base and test URL, where base is the current version of Frontier and test is the version you want to test.

frontier-cmp -t https://new-frontier.host.org -b https://frontier.digitalbits.io

The paths to be tested can be found in init_paths.go.

ELB access log

To run using an ELB access log, use the flag -a.

frontier-cmp -t https://new-frontier.host.org -b https://frontier.digitalbits.io -a ./elb_access.log

Additionally you can specify which line to start in by using the flag -s.

History

You can use the history command to compare the history endpoints for a given range of ledgers.

frontier-cmp history -t https://new-frontier.domain.org -b https://base-frontier.domain.org

By default this command will check the last 120 ledgers (~10 minutes), but you can specify --from and --to.

frontier-cmp history -t https://new-frontier.domain.org -b https://base-frontier.domain.org --count 20

or

frontier-cmp history -t https://new-frontier.domain.org -b https://base-frontier.domain.org --from 10 --to 20

Request per second

By default frontier-cmp will send 1 request per second, however, you can change this value using the --rps flag. The following will run 10 request per second. Please note that sending too many requests to a production server can result in rate limiting of requests.

frontier-cmp -t https://new-frontier.host.org -b https://frontier.digitalbits.io --rps 10