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

DTT2 - Iteration 3 - Unit test - Unit tests for each module #4993

Open
2 of 3 tasks
Tracked by #4495
fcaffieri opened this issue Feb 21, 2024 · 1 comment
Open
2 of 3 tasks
Tracked by #4495

DTT2 - Iteration 3 - Unit test - Unit tests for each module #4993

fcaffieri opened this issue Feb 21, 2024 · 1 comment

Comments

@fcaffieri
Copy link
Member

fcaffieri commented Feb 21, 2024

Epic: #4495


Description

The objective of this issue is to generate automated unit tests for each module.

Taks

Resources

Observations/Requirements

  • Pytest will be used to develop the unit test
  • Minimum execution according to changes, but for now each module will be tested in full
    • To be improved in the future
  • Tests should be executed locally and through GitHub Actions
  • The GitHub Actions workflows should allow to be run on demand

Branch

@wazuhci wazuhci moved this to Triage in Release 4.9.0 Feb 21, 2024
@fcaffieri fcaffieri changed the title Generate automated unit tests for each module DTT1 - Iteration 3 - Unit test - Unit tests for each module Feb 21, 2024
@wazuhci wazuhci moved this from Triage to Backlog in Release 4.9.0 Feb 21, 2024
@rauldpm rauldpm added level/task Task issue and removed level/task Task issue labels Mar 20, 2024
@rauldpm rauldpm changed the title DTT1 - Iteration 3 - Unit test - Unit tests for each module DTT2 - Iteration 3 - Unit test - Unit tests for each module Mar 21, 2024
@fcaffieri
Copy link
Member Author

The issue is moved to DTT2 since it was not within the requirements or scope of DTT1.

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

When branches are created from issues, their pull requests are automatically linked.

2 participants