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

Enhance QA tests for Vulnerability Detection to display failures reasons #23226

Closed
3 tasks done
GabrielEValenzuela opened this issue May 3, 2024 · 2 comments · Fixed by #23457
Closed
3 tasks done
Assignees
Labels
level/task type/enhancement New feature or request

Comments

@GabrielEValenzuela
Copy link
Member

GabrielEValenzuela commented May 3, 2024

Problem Description

The current Quality Assurance (QA) testing framework for Vulnerability Detection lacks a feature to explicitly display when a test fails. This omission makes the debugging process challenging and time-consuming, as developers must manually sift through logs or other outputs to identify and understand the source of failures.

Expected Behavior

The QA testing process for Vulnerability Detection should include clear and immediate feedback when a test fails, detailing the specific test case and reasons for failure. This enhancement will significantly streamline the debugging process, enabling quicker identification and resolution of issues.

Steps to Reproduce

N/A - This issue relates to the enhancement of existing QA testing procedures.

Definition of Done Checklist

  • Implement enhancements in the QA testing framework to display detailed failure messages for each failed test.
  • Ensure that failure messages include sufficient information to understand the context and cause of the failure.
  • Test the new failure display functionality to ensure it meets the needs of developers.

@sebasfalcone
Copy link
Member

Update

Moved in progress, changes base from master to 4.8.0

@pereyra-m
Copy link
Member

Update

Rebased, moving to pending review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task type/enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants