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

Improve K6 test outcome for better failure insights #703

Open
Ahmed-Ghanam opened this issue Feb 5, 2025 · 0 comments
Open

Improve K6 test outcome for better failure insights #703

Ahmed-Ghanam opened this issue Feb 5, 2025 · 0 comments
Labels
kind/chore Non functional, often repeating tasks. status/draft Status: When you create an issue before you have enough info to properly describe the issue.

Comments

@Ahmed-Ghanam
Copy link
Contributor

Description

Description:

Our current K6 performance tests provide valuable insights, but they lack detailed failure information when tests fail. Diagnosing issues requires manually checking Application Insights, adding extra time and effort. Enhancing the test outcomes with enriched failure details would help us quickly identify and resolve issues.

Issues identified:

  • Time-consuming debugging: Identifying the root cause of a failure requires additional effort since logs are not immediately available in test reports.
  • Limited test outcome visibility: Error messages, stack traces, and request/response details are not easily accessible in the test results.

Proposed improvements:

  1. Enhance failure reporting in K6 logs
    • Include detailed error messages directly in the test output.
  2. Improve integration with application insights
    • Provide links or summary data from Application Insights within the test output.
  3. Streamline debugging process
    • Format test results for better readability.
    • Provide structured failure reports with key debugging information.

Acceptance criteria:

  • K6 test failures include detailed, actionable insights.
  • Enhanced logging and reporting reduce the need to manually check Application Insights.
  • Test outcome visibility is improved with structured error messages.

Additional Information

No response

Tasks

No response

Acceptance Criterias

No response

@Ahmed-Ghanam Ahmed-Ghanam added kind/chore Non functional, often repeating tasks. status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/chore Non functional, often repeating tasks. status/draft Status: When you create an issue before you have enough info to properly describe the issue.
Projects
None yet
Development

No branches or pull requests

1 participant