zeegin / zeegin/OpenSubsystemsLibrary
Prettify assert actual and expected values
Nobody has claimed this yet.
- Dominant language
- 1C Enterprise
- Stars
- 85
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
When unit tests raise assert error we shuld pass actual and expected values.
But this values can be non primitive.
It include some references or collections.
To better marge-view in JUnit panel is shuld be full printed values, including types, collection items or structure properties.
Open question is how prettify nested collections? Maybe we must convert it to json.
Contributor guide
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 unit-test assertion error path and the code that supplies values to the JUnit panel. Compare how primitive and non-primitive actual and expected values are currently represented. Define the required output for references, collections, types, and nested structures before choosing how completion will be verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100