From 2550f89d6c8cfcd6340d7a94e9947e780abc9d42 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?David=20Santiago=20Turi=C3=B1o?= Date: Fri, 20 Mar 2026 08:24:40 +0100 Subject: [PATCH] Snaptesting notice --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index 221836e..f6cef65 100644 --- a/README.md +++ b/README.md @@ -7,12 +7,18 @@ Logs snapshot testing for Android Instrumentation tests. +> [!IMPORTANT] +> Loggerazzi has evolved into [Android Snaptesting](https://github.com/Telefonica/android-snaptesting), which is now the recommended library for new projects. +> This repository remains available for existing integrations and historical reference. + ## Introduction Similarly to screenshot testing, which is an easy and maintainable approach to ensure your application UI does not get broken, Loggerazzi brings the same "snapshoting" idea, but for your analytics or any other application logs. ## Usage +For new integrations, use [Android Snaptesting](https://github.com/Telefonica/android-snaptesting) instead of Loggerazzi. + You just need to include the Loggerazzi plugin in your project, and the rule in your test class (configuring it properly). In order to universally include all your existing application tests, rule can be added to your tests base class.