refactor: improve test capability and coverage #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
I'm prototyping
libvips
-based Morandi on a separate branch in hope of improving its memory profile and performanceProblem
The specs only check for presence of output files and do little to assess their content, requiring manual visual inspection
Solution
Introduce:
Notes
ensure
keyword available in blocks (2.5+)Gemfile.lock
for smoother Development experience (otherwise it's often required to runbundle install
after launching the container because of some gems getting outdated)Screenshots
tmp/reference-image-matches/morandi_spec-rb-512/reference.jpg
)tmp/reference-image-matches/morandi_spec-rb-512/tested.jpg
) after disabling colour profile conversion (there's clear colour difference caused by stripping colour profile information without proper conversion)tmp/reference-image-matches/morandi_spec-rb-512/diff.jpg
after disabling colour profile conversion (red-ish pixels indicate colour mismatch)