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

DATAGO-70002: Status on CommandMessage tests #162

Merged

Conversation

CameronRushton
Copy link
Collaborator

What is the purpose of this change?

Add a couple tests to ensure this works probably

How was this change implemented?

Added two tests that check different error scenarios.
I also tried adding a test for the case where the CommandType is unknown. Seems like it's not possible with JUnit5 because we need something like (at)BeforeClass and some tricky mocking of the CommandType enum to add a fake type.
Alternatively, we could apparently make another copy of that enum in the test package and use that one instead, but that seemed poor and would only work with maven and some trickery. Probably not worth it but cool to try.

How was this change tested?

I ran the tests

Is there anything the reviewers should focus on/be aware of?

...

Copy link

SonarQube Quality Gate

Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@gregmeldrum gregmeldrum merged commit 96a7602 into greg/DATAGO-70002-import Feb 9, 2024
6 checks passed
@mo-radwan1 mo-radwan1 deleted the crushton/DATAGO-70002_status_on_request branch May 7, 2024 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants