From c3c71dddbe9409691585cd76f31243526dd478d0 Mon Sep 17 00:00:00 2001
From: Stevan Freeborn <65925598+StevanFreeborn@users.noreply.github.com>
Date: Sat, 30 Nov 2024 17:04:58 -0600
Subject: [PATCH] posts: add intro

---
 .../index.md                                           | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/Blog/wwwroot/posts/making-visual-regression-testing-more-manageable-with-playwright/index.md b/src/Blog/wwwroot/posts/making-visual-regression-testing-more-manageable-with-playwright/index.md
index e02d779..319786a 100644
--- a/src/Blog/wwwroot/posts/making-visual-regression-testing-more-manageable-with-playwright/index.md
+++ b/src/Blog/wwwroot/posts/making-visual-regression-testing-more-manageable-with-playwright/index.md
@@ -7,3 +7,13 @@
   "openGraphImage": "posts/making-visual-regression-testing-more-manageable-with-playwright/og-image.png",
 }
 ```
+
+Recently I've been working to add a set of automated end-to-end smoke tests to cover reports within [Onspring](https://www.onspring.com/). Reports are a key feature of the platform and one of the key aspects of the reports is the ability to present the data within the reports in visually appealing and interesting ways using a variety of chart types. Initially I had taken the approach of building the reports and then asserting that particular aspects of the report were present in the DOM with the expected data. It worked, but then I remembered that [Playwright](https://playwright.dev/) has a whole set of features for doing visual regression testing and I hadn't yet had a good opportunity to put them to use. This use case seemed like a perfect fit.
+
+## The Plan
+
+## The Problem
+
+## The Solution
+
+## Conclusion