Method is missed in assertion amplification
Nobody has claimed this yet.
- Dominant language
- Smalltalk
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
In amplification of DTTestCoverageTest asserting the value of startButtonHelp increases the coverage. It's generated after a. direct method added by input amplification:
aString := plugin startButtonHelp.
self assert: aString equals: 'Run test coverage in selected packages'
I expect the assertion for asserting the value of startButtonHelp be created in assertion amplification, not after a direct input amp.
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 locating the amplification logic exercised for DTTestCoverageTest and trace how startButtonHelp is introduced and asserted. Compare assertion amplification with direct input amplification, then verify that the startButtonHelp assertion is generated by the former rather than appearing after the latter. Done means the amplified output places this assertion in assertion amplification.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100