in the [Jest 3 testing fails list](https://gitlab-org.gitlab.io/frontend/playground/jest-speed-reporter/vue3.html) we have a couple of failures because of undefined img sources. Example: ``` diffs/components/commit_item default state renders author avatar / spec/frontend/diffs/components/commit_item_spec.js (0.019s) Error: expect(received).toBe(expected) // Object.is equality Expected: "https://www.gravatar.com/avatar/d6d28ea7f1c7f9b7f2fbdd19785661cf3b570cd5c2fcffe958c08b0e9dd361d9?s=80&d=identicon" Received: undefined at Object.toBe (/builds/gitlab-org/gitlab/spec/frontend/diffs/components/commit_item_spec.js:84:44) at Object.asyncJestTest (/builds/gitlab-org/gitlab/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:125:37) at /builds/gitlab-org/gitlab/node_modules/jest-jasmine2/build/queueRunner.js:41:12 at new Promise (<anonymous>) at mapper (/builds/gitlab-org/gitlab/node_modules/jest-jasmine2/build/queueRunner.js:28:19) at /builds/gitlab-org/gitlab/node_modules/jest-jasmine2/build/queueRunner.js:68:41 ``` This happens on specs using the `mount` method (instead of `shallowMount`). A possible fix is to replace testing the `img` element itself, but testing the properties passed down to the component. If there is no component to test, but `img` is used directly, we need another solution.