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

Continuously develop unit tests #34

Open
Bronzila opened this issue Jun 27, 2023 · 0 comments
Open

Continuously develop unit tests #34

Bronzila opened this issue Jun 27, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@Bronzila
Copy link
Collaborator

In order to ensure, that the mechanics of DEHB function correctly (especially after changes/refactorings), it would be helpful to develop unit tests.

These could be divided into three major categories:

  1. DEHB
  2. Bracket Manager
  3. DE

I would prioritize these test as given by the order of the list above, since DEHB itself and the bracket manager are more likely to be adjusted in the future and therefore the unit tests will act like a safety net to ensure the components still work as they are supposed to.

Depending on which DE implementation we used, there might even be some unit tests in the original repo or did you write the DE code yourself? @Neeratyoy

@Bronzila Bronzila added the enhancement New feature or request label Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant