Skip to content
This repository has been archived by the owner on Oct 25, 2024. It is now read-only.

Create a suite of QA tests #1243

Closed
ra0x3 opened this issue Aug 9, 2023 · 1 comment · Fixed by #1348
Closed

Create a suite of QA tests #1243

ra0x3 opened this issue Aug 9, 2023 · 1 comment · Fixed by #1348
Assignees

Comments

@ra0x3
Copy link
Contributor

ra0x3 commented Aug 9, 2023

  • As a part of Revamp our testing suite and CI #1226 we need to add some type of QA testing
  • These QA tests would be different from unit tests (#[test]) and integration tests (forc index {do a thing})
  • QA tests would be run out-of-band from CI
    • Ideally they would be run in order to ensure a release is OK to go out - but that's not a hard requirement for now
  • QA tests are tests that:
    • Don't necessarily start at block 0
      • They start from arbitrary blocks
      • Run much longer than tests on CI
        • Around ~10 minutes (rough guess)
        • Monitor various metrics of indexer performance
          • These various metrics include things like: CPU usage, memory usage, and indexer accuracy
            • Any significant change in any of these ☝🏽 metrics could potentially have a significant adverse effect on the block explorer
  • If we're going to be shipping a production block explorer, we simply cannot afford to release bad code - therefore we need these QA tests
@ra0x3 ra0x3 added the P: Medium label Aug 9, 2023
@ra0x3 ra0x3 self-assigned this Aug 16, 2023
@ra0x3
Copy link
Contributor Author

ra0x3 commented Aug 17, 2023

Perhaps we investigate the usage of https://tokio.rs/blog/2023-01-03-announcing-turmoil

@ra0x3 ra0x3 linked a pull request Sep 12, 2023 that will close this issue
12 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant