UnitTestBot / UnitTestBot/usvm
Generating tests for one method returns less test cases than for the whole class
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 33
- Forks
- 27
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 15
Description
Consider two following scenarios of tests generation:
timeLimit = 60
methodFilter = "org.usvm.samples.wrappers.LongWrapper.*"
projectFilter = listOf("samples")
and
timeLimit = 60
methodFilter = "org.usvm.samples.wrappers.LongWrapper.parseLong"
projectFilter = listOf("samples")
First scenario allows to get several tests, and for the function parseLong too.
In the second scenario no test cases were generated by the machine.
Also note that there are no tests with timeLimit=20 at all...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the two configurations for org.usvm.samples.wrappers.LongWrapper, comparing the class wildcard with the method filter for parseLong and checking the timeLimit=20 case. Trace the test-generation entry point used by these filters; done means method-level generation produces the expected tests consistently with class-level generation, including at the shorter limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kotlin
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100