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

The jump to source feature only works if the test are executed from package level #133

Open
Drakojin opened this issue May 29, 2020 · 6 comments
Labels

Comments

@Drakojin
Copy link
Contributor

Specification

LivingDoc-Version:
Platform: Windows 10
Subsystem:

Describe the bug
The Step and Field Result have no TestSource when single Document is executed

Expected behavior
I can jump to the Method that executed the step or check when executing a single document.

To Reproduce
Steps to reproduce the behavior:

Open IDE
Open a Test containing a Document
Execute the Document
Right click on a Step or Field result
@Drakojin Drakojin added the bug label May 29, 2020
@Drakojin
Copy link
Contributor Author

How are you running your tests?
Specifically, which IDE are you using and are you running your tests using Gradle or JUnit?

@Drakojin
Copy link
Contributor Author

I tried to reproduce the issue.
When running the tests using IntelliJ the jump to source feature works for Steps and Checks.
When running using Gradle, the jump to source feature is not working.
This is a problem already documented in # 18 (closed) and marked as won't fix

@Drakojin
Copy link
Contributor Author

With using IntelliJ to build, compile and run the tests it works.

@Drakojin
Copy link
Contributor Author

The class source works now with gradle so part of # 18 (closed) is fixed, but the methods don't work.

@Drakojin
Copy link
Contributor Author

the problem described by # 18 (closed) is mainly that the test are not executed at all and gradle have a deadlock. We can upgrade to gradle 6.x to fix this issue

@Drakojin
Copy link
Contributor Author

It seems that this is a problem with Gradle.
Before upgrading to Gradle 6.x we should talk to the POs about that.

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