diff --git a/Readme.md b/Readme.md
index 457c1c39b..a4fd1ed0d 100644
--- a/Readme.md
+++ b/Readme.md
@@ -12,7 +12,7 @@ Highlights:
 - Execute fully self-contained, repeatable, parallelizable automated UI tests on Orchard Core apps.
 - Do cross-browser testing with all current browsers, both in normal and headless modes.
 - Check the HTML structure and behavior of the app, check for errors in the Orchard logs and browser logs. Start troubleshooting from the detailed full application dumps and test logs if a test fails.
-- Start tests with a setup using recipes, start with an existing Orchard Core app or take snapshots in between tests and resume from there. Use SQLite or SQL Server database snapshots (but you can also use PostgreSQL or MySQL too without snapshots).
+- Start tests with a setup using recipes, start with an existing Orchard Core app or take snapshots in between tests and resume from there. Use SQLite or SQL Server database snapshots (but you can also use PostgreSQL or MySQL too without snapshots, see [this proof of concept](https://github.com/OrchardCMS/OrchardCore/pull/11194/files)).
 - Use local file storage or Azure Blob Storage for Media.
 - Test e-mail sending with a local SMTP server too. Everything just works.
 - Built-in tests to check that basic Orchard Core features work, like login, registration, and content management. Demo video [here](https://www.youtube.com/watch?v=jmhq63sRZrI). And a [demo video](https://www.youtube.com/watch?v=BwHoLmgrV9g) about a proof of concept to add UI testing to Orchard.