Invalid data is generated when we use default constructors
Open
Nobody has claimed this yet.
- Dominant language
- Smalltalk
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
testAddNumericColumnNamedEvaluated_amp_A14
| evaluationBlock lastColumnDescription tmp_ihsjUncFWx1 tmp_zT6PFs65HH2 tmp_16NrekBxkO1 |
evaluationBlock := [ :x | x asInteger ].
tmp_ihsjUncFWx1 := table
addNumericColumnNamed: 'numeric'
evaluated: evaluationBlock.
tmp_16NrekBxkO1 := tmp_ihsjUncFWx1
addButtonColumnNamed: 'test'
iconName: 'delete'
onClick: BlockClosure new
tooltip: 'Example tooltip.'.
tmp_zT6PFs65HH2 := table columnDescriptions.
lastColumnDescription := tmp_zT6PFs65HH2 last
having BlockClosure new causes an error in assertion generation.
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 with the test named testAddNumericColumnNamedEvaluated_amp_A14 and reproduce the failure caused by BlockClosure new in the onClick argument. Trace the assertion-generation path from this test and determine which default-constructed value produces invalid data. Done means the test no longer errors during assertion generation when using the default constructor.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100