Skip to content

test(perf): add k6 load test for verify endpoint (#350)#441

Merged
dev-fatima-24 merged 1 commit into
dev-fatima-24:mainfrom
daree-dev:feat/issue-350-verify-perf-tests
Jun 1, 2026
Merged

test(perf): add k6 load test for verify endpoint (#350)#441
dev-fatima-24 merged 1 commit into
dev-fatima-24:mainfrom
daree-dev:feat/issue-350-verify-perf-tests

Conversation

@daree-dev
Copy link
Copy Markdown
Contributor

@daree-dev daree-dev commented May 31, 2026

  • Rewrite backend/load-test.js to target /v1/verify/public/:wallet (no auth)
  • Two scenarios: cached (100 VUs, same wallet) and uncached (100 VUs, unique wallets)
  • Thresholds: cached p95<500ms, uncached p95<2000ms, error rate<1%
  • Uses k6-summary textSummary; outputs load-test-results.json + load-test-summary.json
  • Add verify-perf job to ci.yml: starts backend, installs k6, runs test, uploads artifacts (90d)
  • Include verify-perf in all-tests gate

Description

Please include a summary of the changes and related context

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Changes Made

Testing

Please describe the tests you ran and how to reproduce them:

  • Unit tests pass
  • Integration tests pass
  • Manual testing completed

Test Coverage:

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests passed locally with my changes
  • Any dependent changes have been merged and published
  • If this PR adds a new directory or key file, I have updated docs/folder-structure.md.

Screenshots (if applicable)

If your changes include UI modifications, please add screenshots here.

Additional Notes

Any additional information that reviewers should know.
closes #350

- Rewrite backend/load-test.js to target /v1/verify/public/:wallet (no auth)
- Two scenarios: cached (100 VUs, same wallet) and uncached (100 VUs, unique wallets)
- Thresholds: cached p95<500ms, uncached p95<2000ms, error rate<1%
- Uses k6-summary textSummary; outputs load-test-results.json + load-test-summary.json
- Add verify-perf job to ci.yml: starts backend, installs k6, runs test, uploads artifacts (90d)
- Include verify-perf in all-tests gate
@drips-wave
Copy link
Copy Markdown

drips-wave Bot commented Jun 1, 2026

@daree-dev Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@dev-fatima-24 dev-fatima-24 merged commit 88d08ac into dev-fatima-24:main Jun 1, 2026
4 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[TESTING] Write performance tests for verify endpoint under load

2 participants