From 692d3d1d1b70e9fdabb4d5881960c29102ccd94a Mon Sep 17 00:00:00 2001
From: Meysam Hadeli <35596795+meysamhadeli@users.noreply.github.com>
Date: Thu, 5 Oct 2023 22:51:23 +0330
Subject: [PATCH] Update README.md

---
 README.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 445fa89..4f62684 100644
--- a/README.md
+++ b/README.md
@@ -35,14 +35,15 @@
 - :sparkle: Using `Event Store` for `write side` of Booking-Microservice to store all `historical state` of aggregate.
 - :sparkle: Using `Inbox Pattern` for ensuring message idempotency for receiver and `Exactly once Delivery`. 
 - :sparkle: Using `Outbox Pattern` for ensuring no message is lost and there is at `At Least One Delivery`.
-- :sparkle: Using `Unit Testing`, `Integration Testing`, `End To End Testing` for testing level.
+- :sparkle: Using `Unit Testing` for testing small units and mocking our dependencies with `Nsubstitute`.
+- :sparkle: Using `End To End Testing` and `Integration Testing` for testing features with all dependencies with `testcontainers`.
 - :sparkle: Using `Fluent Validation` and a `Validation Pipeline Behaviour` on top of `MediatR`.
 - :sparkle: Using `Minimal API` for all endpoints.
 - :sparkle: Using `Health Check` for `reporting` the `health` of app infrastructure components.
 - :sparkle: Using `Docker-Compose` and `Kubernetes` for our deployment mechanism.
 - :sparkle: Using `Kibana` on top of `Serilog` for `logging`.
-- :sparkle: Using `Jaeger` on top of `OpenTelemetry` for `tracing`.
-- :sparkle: Using `Prometteuse` and `Grafana` on top of `OpenTelemetry` for `monitoring`.
+- :sparkle: Using `OpenTelemetry` for distributed tracing top of `Jaeger`.
+- :sparkle: Using `OpenTelemetry` for monitoring top of `Prometteuse` and `Grafana`.
 - :sparkle: Using `IdentityServer` for authentication and authorization base on `OpenID-Connect` and `OAuth2`.
 - :sparkle: Using `Yarp` as a microservices `gateway`.
 - :sparkle: Using `Kubernetes` to achieve efficient `scaling` and ensure `high availability` for each of our microservices.