To help ensure the reliability of the filecoin explorer, we should automate the "generation" of the fixture data used in the tests. The fixture information should be able to be sourced from a single filecoin node by pointing a script to the nodes api.
This automation will help ensure we have "real world" data used in the testing.
Additional automation (in the form of nightly cron) could be used to fetch data from the nightly devnet and run the tests, with periodic updates commited back when data structures change (resulting in failures of the automated nightly tests).
Acceptance Criteria
- Fixture data can be updated through a script
- Tests should be written in a way such that minimal code changes are needed due to changing cid values.
To help ensure the reliability of the filecoin explorer, we should automate the "generation" of the fixture data used in the tests. The fixture information should be able to be sourced from a single filecoin node by pointing a script to the nodes api.
This automation will help ensure we have "real world" data used in the testing.
Additional automation (in the form of nightly cron) could be used to fetch data from the nightly devnet and run the tests, with periodic updates commited back when data structures change (resulting in failures of the automated nightly tests).
Acceptance Criteria