From 3652a897796ea0bc7df43e0d4ed597be3b8187c4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Valentin=20Breu=C3=9F?= Date: Sun, 11 Oct 2026 07:42:42 +0200 Subject: [PATCH] docs: mention migration analyzer when switiching to Testably Points users switching to Testably at the analyzer that automates most of the migration. --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 64b50d973..b8b51be8f 100644 --- a/README.md +++ b/README.md @@ -170,7 +170,11 @@ Both projects share the same maintainer, but active development and new features - Active development and new features ### Migrating from TestableIO -Switching from TestableIO to Testably only requires changes in your test projects: +Switching from TestableIO to Testably only requires changes in your test projects. + +The [`Testably.Abstractions.Migration`](https://docs.testably.org/Abstractions/migration-from-testableio/Migration/) analyzer can automate most of this: it flags TestableIO usages in your tests and offers code fixes to rewrite them for Testably. Install it temporarily, apply the fixes (e.g. via `dotnet format analyzers`), then remove it again. + +To migrate manually: 1. Replace the NuGet package reference in your test projects: ```xml