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

Failing Unit Tests #37

Open
MelbourneDeveloper opened this issue Sep 25, 2024 · 0 comments
Open

Failing Unit Tests #37

MelbourneDeveloper opened this issue Sep 25, 2024 · 0 comments
Labels

Comments

@MelbourneDeveloper
Copy link
Collaborator

MelbourneDeveloper commented Sep 25, 2024

Most unit tests that compile pass. However, some tests create different results to the original, and it's not clear why. This may be related to the new Mockito mocks.

These tests have been marked with skip=true so the builds succeed. But, long term, we need to either a) fix the bug/test, or b) deem the test to be invalid for some reason.

If it's invalid, we will delete the test and write something like "Original Test Invalid" as a comment where the original test was.

These are tests are marked with:

// TODO: Failing Test

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

No branches or pull requests

1 participant