118 lines
5.1 KiB
YAML
118 lines
5.1 KiB
YAML
uuid:
|
|
- value: 5563fb1b-a5a1-4372-84b9-b0be87acc501
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-05-11T09:00:18+00:00'
|
|
revision_uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
revision_log: { }
|
|
status:
|
|
- value: true
|
|
uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
title:
|
|
- value: 'Visual testing and Diffy with Yuri Gerasymov'
|
|
created:
|
|
- value: '2024-03-10T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:18+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2024/03/10/visual-testing-and-diffy-with-yuri-gerasymov
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>This week on the Beyond Blocks podcast, I'm joined by Yuri Gerasymov to discuss Diffy visual regression testing.</p>
|
|
|
|
<h2 id="talking-points">Talking Points</h2>
|
|
|
|
<ul>
|
|
<li>What is visual regression testing?</li>
|
|
<li>How do you deal with false positives?</li>
|
|
<li>Different use cases for visual regression testing.</li>
|
|
<li>Automatic updates.</li>
|
|
<li>Scheduling content.</li>
|
|
<li>Visual regression testing in CI.</li>
|
|
<li>Diffy in WordPress.</li>
|
|
<li>What's a baseline?</li>
|
|
<li>Initial setup and onboarding feedback.</li>
|
|
<li>Testing dark mode?</li>
|
|
<li>Component testing with Storybook and Fractal?</li>
|
|
<li>Testing local environments.</li>
|
|
<li>Testing as authenticated users.</li>
|
|
<li>The roadmap for Diffy.</li>
|
|
</ul>
|
|
|
|
<h2 id="quotable-quotes">Quotable Quotes</h2>
|
|
|
|
<ul>
|
|
<li>We help development teams to have less visual bugs in their website. We take screenshots of the pages and compare them so you can see what changed and how. (YG)</li>
|
|
<li>We built tools for you to mock the content. You provide selectors for the elements with the content of the article and we'll replace it with lorem ipsum text so it will be exactly the same across multiple environments. (YG)</li>
|
|
<li>I can still write an assertion to check the text is on the page or not, but it won't confirm it's in the correct place. (OD)</li>
|
|
<li>Having a tool checking for changes on a regular basis instead of only after a deployment would be very useful. (OD)</li>
|
|
<li>So, you could have a tool like Violinst automatically creating pull requests and Diffy checking those PRs, so the two could work together? (OD)</li>
|
|
<li>With visual testing, it's very easy to get started. (YG)</li>
|
|
<li>Visual testing is great for showing your client your work. (YG)</li>
|
|
</ul>
|
|
|
|
<p>I learned a lot during this conversation and have added visual regression testing to my testing toolbox for working on projects.</p>
|
|
|
|
<p><a href="/podcast/14-yuri-gerasymov-diffy">Listen to the episode</a></p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>This week on the Beyond Blocks podcast, I'm joined by Yuri Gerasymov to discuss Diffy visual regression testing.</p>
|
|
|
|
<h2 id="talking-points">Talking Points</h2>
|
|
|
|
<ul>
|
|
<li>What is visual regression testing?</li>
|
|
<li>How do you deal with false positives?</li>
|
|
<li>Different use cases for visual regression testing.</li>
|
|
<li>Automatic updates.</li>
|
|
<li>Scheduling content.</li>
|
|
<li>Visual regression testing in CI.</li>
|
|
<li>Diffy in WordPress.</li>
|
|
<li>What's a baseline?</li>
|
|
<li>Initial setup and onboarding feedback.</li>
|
|
<li>Testing dark mode?</li>
|
|
<li>Component testing with Storybook and Fractal?</li>
|
|
<li>Testing local environments.</li>
|
|
<li>Testing as authenticated users.</li>
|
|
<li>The roadmap for Diffy.</li>
|
|
</ul>
|
|
|
|
<h2 id="quotable-quotes">Quotable Quotes</h2>
|
|
|
|
<ul>
|
|
<li>We help development teams to have less visual bugs in their website. We take screenshots of the pages and compare them so you can see what changed and how. (YG)</li>
|
|
<li>We built tools for you to mock the content. You provide selectors for the elements with the content of the article and we'll replace it with lorem ipsum text so it will be exactly the same across multiple environments. (YG)</li>
|
|
<li>I can still write an assertion to check the text is on the page or not, but it won't confirm it's in the correct place. (OD)</li>
|
|
<li>Having a tool checking for changes on a regular basis instead of only after a deployment would be very useful. (OD)</li>
|
|
<li>So, you could have a tool like Violinst automatically creating pull requests and Diffy checking those PRs, so the two could work together? (OD)</li>
|
|
<li>With visual testing, it's very easy to get started. (YG)</li>
|
|
<li>Visual testing is great for showing your client your work. (YG)</li>
|
|
</ul>
|
|
|
|
<p>I learned a lot during this conversation and have added visual regression testing to my testing toolbox for working on projects.</p>
|
|
|
|
<p><a href="/podcast/14-yuri-gerasymov-diffy">Listen to the episode</a></p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|