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

QA Planning: Adding to the MSU hotfixes collected by the Catalog #3288

Closed
4 tasks done
Deblintrake09 opened this issue Sep 14, 2022 · 1 comment
Closed
4 tasks done
Assignees

Comments

@Deblintrake09
Copy link
Contributor

Deblintrake09 commented Sep 14, 2022

Description

This problem aims to investigate https:/wazuh/wazuh-tools/pull/195 to define the test cases to be carried out.

Development stage

  • Research the applied change.
  • Research if we have a test for this case.
  • Define the test cases. Identify the base cases, and then the rest of the tests as tier 2.
  • Define whether it is necessary to test systems, integration, or E2E. Create the corresponding issues.
@Deblintrake09
Copy link
Contributor Author

Research if we have a test for this case

Currently we have IT tests for VDT that check the correct alert generation. Nonetheless, this PR adds data to the MSU feed that cannot be detected by wazuh with the vulnerability information that can be collected from the catalog, since the new data has no vulnerabilities associated.

Define whether it is necessary to test systems, integration, or E2E. Create the corresponding issues.

New IT tests could be generated as part of the current VDT test suite, with a custom feed to generate alerts associated to the new MSU feed information. For this, the Issue #3361 has been created.

Manual testing will be done for this on Issue #3360

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants