Skip to content

Restructure the manual to tell a story #71

@mkutz

Description

@mkutz

The manual could be more explicit on possible motivations for using ApproveJ.
It could generally tell more of a story of how a sad test code base gets transformed into a better one with ApproveJ.

It could start with a test with >10 assertions on a nested result object.
Replace these with just one approval.
Point out how the approval actually tests more, not less.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions