8000 qa: Expanded stress testing of CometBFT releases · Issue #2028 · cometbft/cometbft · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

qa: Expanded stress testing of CometBFT releases #2028

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
Open
adizere opened this issue Jan 12, 2024 · 0 comments
Open

qa: Expanded stress testing of CometBFT releases #2028

adizere opened this issue Jan 12, 2024 · 0 comments
Labels
major-priority A major, long-running priority for the team qa Quality assurance

Comments

@adizere
Copy link
Member
adizere commented Jan 12, 2024 •
edited
Loading

Summary

As part of our public goods roadmap for 2024, a major priority for us is to continue improving our QA infrastructure and expand the stress testing we do.

This is a tracking issue. It is subject to frequent change, as it is tracking the ongoing work associated with this major priority.

Associated issues

### ABCI
- [ ] #1404 
- [ ] #353
- [ ] #1581
- [ ] https://github.com/cometbft/cometbft/issues/2065

### Infra
- [ ] #51
- [ ] #1204
- [ ] #2022
- [ ] #1754
- [ ] #1354
- [ ] #1061
- [ ] https://github.com/cometbft/cometbft/issues/2107
@adizere adizere added major-priority A major, long-running priority for the team qa Quality assurance labels Jan 12, 2024
@adizere adizere added this to CometBFT Jan 12, 2024
@github-project-automation github-project-automation bot moved this to Todo in CometBFT Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
major-priority A major, long-running priority for the team qa Quality assurance
Projects
No open projects
CometBFT
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@adizere
0