Description

First-take of detailed tests to be run against contributing instances from monitoring, or locally during development/instance verification.
To consider:

1. Not all endpoints are covered, but all sections are covered (e.g. pool_info tested but pool_blocks not). To be decided if we want to test more or less endpoints (list of tested endpoints included below).
2. Figure out how exactly is it going to be integrated with monitoring instances to perform these checks against all nodes in the topology. This is to be covered in the next PR, but the current implementation allows specifying the local/compare nodes from the command line (example below).

Endpoints Tested

Network

• /tip [removed]
• /genesis
• /totals

Epoch

• /epoch_info
• /epoch_params

Block

• /block_info
  Transactions
• /tx_info

Address

• /address_info

Account

• /account_info

Asset

• /asset_info
• /asset_address_list

Pool

• /pool_list
• /pool_info

Script

• /native_script_list

Where should the reviewer start?

Tests can be executed locally by setting up the test env with setup-tests.py and then running pytest from tests directory. This runs with default params specified in tests/conftest.py. You can pass in the parameters via the command line:
pytest --local-url https://eden-guildnet.koios.rest:8453/api/v0 --compare-url https://guild.koios.rest/api/v0 --api-schema-file ../specs/results/koiosapi-guild.yaml

To specify specific test files:
pytest -s test_totals_endpoint.py

Motivation and context

We need more detailed testing to continually verify both our API schema with calls that are not covered by examples in the API spec (schema changes in this PR are the result of inconsistencies found during testing), and that contributing instances are serving healthy data.

Which issue it fixes?

Closes #9

How has this been tested?

Guild:

Testnet:

Mainnet: