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

Expand unrolled spock tests. #3945

Merged
merged 1 commit into from
Apr 11, 2022

Conversation

dbalek
Copy link
Contributor

@dbalek dbalek commented Apr 8, 2022

Support for expanding Spock tests marked with @Unrolled annotation in VSCode Test Explorer.

@dbalek dbalek added the LSP [ci] enable Language Server Protocol tests label Apr 8, 2022
@dbalek dbalek added this to the NB14 milestone Apr 8, 2022
@dbalek dbalek requested review from ppisl and MartinBalin April 8, 2022 11:28
@dbalek dbalek merged commit 9a045e3 into apache:master Apr 11, 2022
@dbalek dbalek deleted the dbalek/unrolled-spock-tests branch April 11, 2022 05:42
@graemerocher
Copy link

I am testing this out and can't seem to expand the unrolled tests with this test https://github.com/micronaut-projects/micronaut-test/blob/master/test-spock/src/test/groovy/io/micronaut/test/spock/MathServiceSpec.groovy

how is this supposed to work?

@MartinBalin
Copy link
Contributor

@graemerocher this is a dev build which changed internal structure for Test explorer to accomodate Spock tests syntax. You need to clear test results as in screenshot
Screenshot 2022-04-12 at 14 18 41

Then you can run the tests and these should expand for @unroll If not make sure test is not running from Gradle cache. It is indicated by output from test run:

> Task :core:compileTestGroovy UP-TO-DATE
> Task :core:testClasses UP-TO-DATE
> Task :core:test FROM-CACHE

It there is core:test FROM-CACHE you need to clear gradle cache or touch the code...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LSP [ci] enable Language Server Protocol tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants