#frame #image #testing #visual #regression #h264 #score


Visual regression testing of H264 frames and images

10 releases (breaking)

0.8.1 May 29, 2024
0.7.0 Dec 16, 2023
0.6.1 Jul 28, 2023

#33 in Video

Download history 903/week @ 2024-02-26 659/week @ 2024-03-04 1146/week @ 2024-03-11 1220/week @ 2024-03-18 978/week @ 2024-03-25 988/week @ 2024-04-01 1227/week @ 2024-04-08 1310/week @ 2024-04-15 1269/week @ 2024-04-22 735/week @ 2024-04-29 529/week @ 2024-05-06 858/week @ 2024-05-13 1520/week @ 2024-05-20 952/week @ 2024-05-27 1078/week @ 2024-06-03 596/week @ 2024-06-10

4,226 downloads per month
Used in 2 crates

MIT license

173 lines


The twenty-twenty library allows for visual regression testing of H.264 frames and images. It makes it easy to update the contents when they should be updated to match the new results.

Each function takes a score threshold, which is the lowest possible "score" you are willing for the image comparison to return. If the resulting score is less than the threshold, the test will fail. The score must be a number between 0 and 1. If the images are the exact same, the score will be 1.

The underlying algorithm is SSIM, which is a perceptual metric that quantifies the image quality degradation that is caused by processing such as data compression or by losses in data transmission. More information can be found here.

You will need ffmpeg installed on your system to use this library. This library uses the ffmpeg bindings in rust to convert the H.264 frames to images.

Use it like this for an H.264 frame:

let actual = get_h264_frame();
twenty_twenty::assert_h264_frame("tests/initial-grid.png", &actual, 0.9);

Use it like this for an image:

let actual = get_image();
twenty_twenty::assert_image("tests/dog1.png", &actual, 0.9);

If the output doesn't match, the program will panic! and emit the difference in the score.

To accept the changes from get_h264_frame() or get_image(), run with TWENTY_TWENTY=overwrite.

Publishing a new release

We have a GitHub action that pushes our releases here. It is triggered by pushing a new tag. So do the following:

  1. Bump the version in Cargo.toml. Commit it and push it up to the repo.
  2. Create a tag with the new version: git tag -sa v$(VERSION) -m "v$(VERSION)"
  3. Push the tag to the repo: git push origin v$(VERSION)


~178K SLoC