diff --git a/.github/workflows/pull_request.yml b/.github/workflows/pull_request.yml
index 73138226..d8e6f730 100644
--- a/.github/workflows/pull_request.yml
+++ b/.github/workflows/pull_request.yml
@@ -47,6 +47,12 @@ jobs:
       - name: Run tests
         run: CI=true sbt test
 
+      - name: Test summary
+        if: always() # Always run, even if previous steps failed
+        uses: test-summary/action@v2
+        with:
+          paths: "**/target/test-reports/*.xml"
+
       - name: Prepare web build
         run: sbt web/build
 
diff --git a/README.md b/README.md
index 93852582..3c0ac692 100644
--- a/README.md
+++ b/README.md
@@ -45,7 +45,7 @@ Deployment 2m demo:
 4. Practical components for testing your server-side code, writing tests for the Data/Api layer is real simple, no excuses accepted.
 5. Practical frontend utilities, for example, test your frontend forms easily, consistent UI when performing asynchronous actions (fetching/submitting data), etc.
 6. Typed data inputs, don't bother running simple validations to form data at the backend, accepted requests are already validated.
-7. Reasonable Continuous-Integration workflows, don't waste time reviewing code format or asking whether tests are passing, Github Actions do this for you.
+7. Reasonable Continuous-Integration workflows, don't waste time reviewing code format, asking whether tests are passing or looking at jobs logs finding which test failed (thanks to [TestForest Dashboard](https://github.com/marketplace/actions/testforest-dashboard) action), Github Actions do this for you.
 8. A simple to follow architecture, including short-guides for doing common tasks. 
 9. Deployment scripts to cloud instances, we believe in simplicity and most projects are fine with simple managed servers instead of containers/K8s/etc.