Add non package/method name paths
- Dominant language
- Java
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Currently, I am using the looksLike matcher to compare images. The problem is that the matcher takes the package name of the caller and uses it to build the path to the image. This way, I must use the matcher directly in my tests and nowhere else.
In my case, I want to use the matcher to create my own. Unfortunately, the looksLike matcher takes the package name of the matcher instead of the actual test method.
Is it possible to change the path/get rid of the "package to path" including feature? And if yes, it would be nice if this would be mentioned in the readme file.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the looksLike matcher and its current package-to-path behavior. Check the README for how matcher paths are documented. Done means callers can provide non-package/method-name paths when creating their own matcher, and the supported behavior is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100