-
-
Notifications
You must be signed in to change notification settings - Fork 27
test(server): add unit tests for extractActionCoords function in ActionCoordsTest
#2140
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
base: main
Are you sure you want to change the base?
Conversation
|
Hi @LeoColman! What's the motivation here? Are you planning to make some adjustments to the logic under test? I'm asking because I think we have good coverage of this part through the end-to-end tests (although I'd have to check when I'm by my laptop). For now just wanted to learn what triggered this PR 😁 |
|
Ah, see it on Slack now, thanks! |
| class ActionCoordsTest : | ||
| FunSpec( | ||
| { | ||
| test("extractActionCoords parses owner/name with version and no path, FULL by default") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about using context("extractActionCoords"), in case we need to add tests for some other function? Then we could remove the function name from individual test cases.
| test("extractActionCoords parses owner/name with version and no path, FULL by default") { | ||
| val parameters = createParameters(owner = "o", name = "act", version = "v1") | ||
|
|
||
| parameters.extractActionCoords(true) shouldBe |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In every test, let's used named arguments - extractActionCoords(true) doesn't look readable.
No description provided.