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

Add support for uri linking per feature and scenario #101

Open
dmi3coder opened this issue Feb 17, 2023 · 3 comments · May be fixed by #102
Open

Add support for uri linking per feature and scenario #101

dmi3coder opened this issue Feb 17, 2023 · 3 comments · May be fixed by #102

Comments

@dmi3coder
Copy link

dmi3coder commented Feb 17, 2023

Currently, dynamic tests don't backlink to a location of scenario or feature.
image
Here I can't locate a file where this feature is defined. It makes the whole process frustrating. It locates me to the main test file that defines those tests:
image

@gsmet
Copy link
Member

gsmet commented Feb 17, 2023

@dmi3coder is it something that can be handled by the extension? If so a PR would be welcome.

@dmi3coder
Copy link
Author

@gsmet I'm trying to hack into it. I see that DynamicTest.dynamicTest accepts URI as a second parameter, which is not passed in a plugin. If i'll get something working I'll create a PR 👍 . Based on some other projects I think that should work

@dmi3coder
Copy link
Author

dmi3coder commented Feb 17, 2023

Yep, my theory worked by passing something like this:

Thread.currentThread().getContextClassLoader().getResource(p.getUri().getSchemeSpecificPart()).toURI()

As second parameter to DynamicTest.dynamicTest.
Will dig deeper over the weekend how to point it to specific line of feature/scenario

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 a pull request may close this issue.

2 participants