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: Add AlmaLinux VDT support #3722

Closed
4 tasks done
Deblintrake09 opened this issue Jan 3, 2023 · 1 comment
Closed
4 tasks done

QA Planning: Add AlmaLinux VDT support #3722

Deblintrake09 opened this issue Jan 3, 2023 · 1 comment

Comments

@Deblintrake09
Copy link
Contributor

Deblintrake09 commented Jan 3, 2023

Description

This problem aims to investigate AlmaLinux support: Add configuration for the new provider) 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

Deblintrake09 commented Jan 4, 2023

Research the applied change.

The applied change adds VDT support for a new provider: AlmaLinux.

Research if we have a test for this case.

Currently there is no test support for this case, but there is support for other VDT providers in the IT suite. Testing for this case should include adding support for this provider in the current suite.

Define the test cases. Identify the base cases, and then the rest of the tests as tier 2.

Test cases for support should be added to the following test suites:

  • test_vulnerability_detector/test_providers
  • test_vulnerability_detector/test_scan_results

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

To handle the IT development the Issue #3723 has been created.
Currently no Manual Testing has been created, until we determine the complexity of adding the IT tests (this depends if there is a different behaviour of if the feed is too different than current feeds and requires new specific tests).

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