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.

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

feat: K6 test result capture #199

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

feat: K6 test result capture #199

wants to merge 4 commits into from

Conversation

jannable
Copy link
Contributor

This PR introduces an automated load testing solution using K6, providing documented evidence of performance tests and capturing specific app/infrastructure versions tested.

Key Features

  • Automated bash script (run_tests.sh) for load testing
  • Flexible test execution (all cases or specific)
  • Command-line argument support
  • Multiple scenario support per test (sequential/concurrent)
  • Timestamped result storage
  • Version tracking (GitHub hashes for app/infrastructure)

Usage

./run_tests.sh [--all | --test <test_case_name>] [OPTIONS]

Impact

  • Consistent load test execution and documentation
  • Performance tracking across versions
  • Trend analysis capability

Next Steps

  • Results visualization dashboard
  • Expand/refine test case coverage

Copy link
Contributor

Coverage report

This PR does not seem to contain any modification to coverable code.

Copy link
Contributor

@juleskuehn juleskuehn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the way the results are saved. I also think we should be saving results elsewhere though. Perhaps this can all go into the infrastructure repo?
And could you save a copy of the original k6_script.js though, so that we retain it for more flexible/ one-off use?

@jannable
Copy link
Contributor Author

The recommended changes are done. Moved to otto-infra, k6_script preserved.

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.

2 participants