Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

QGB base integration test scenarios #407

Closed
Tracked by #301
rach-id opened this issue May 13, 2022 · 0 comments
Closed
Tracked by #301

QGB base integration test scenarios #407

rach-id opened this issue May 13, 2022 · 0 comments
Assignees
@rach-id
Labels
testing items that are strictly related to adding or extending test coverage

Comments

@rach-id
Copy link
Member

rach-id commented May 13, 2022 •
edited
Loading

As of #398, the proposed scenarios are as follows:

Orchestrator tests

  • Test one orchestrator signing attestations
  • Test multiple orchestrators signing attestations
  • Test orchestrator catchup mechanism

Relayer tests

  • Test relayer relaying attestations in the case of 1 validator
  • Test relayer relaying attestations in the case of multiple validators
  • Test relayer late start

Deployer tests

  • Test the deployment of a new QGB contract
@rach-id rach-id added C: QGB testing items that are strictly related to adding or extending test coverage labels May 13, 2022
@rach-id rach-id moved this to TODO in Celestia Node May 13, 2022
This was referenced May 13, 2022
Closed
Merged
@rach-id rach-id self-assigned this May 25, 2022
@rach-id rach-id moved this from TODO to In Review in Celestia Node May 25, 2022
@rach-id rach-id moved this from In Review to Done in Celestia Node May 26, 2022
@rach-id rach-id closed this as completed May 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rach-id rach-id

Labels
testing items that are strictly related to adding or extending test coverage
Projects
No open projects
Celestia Node
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rach-id