Added testing script docs.

README.md

@@ -125,6 +125,61 @@ Determines how the middleware connects to databases:
 
 > **Note:** By default, Docker containers operate on an isolated network. If your database is local, the middleware must be configured to run on the same network to ensure connectivity.
 
+### Test your setup:
+
+Use the `status` command:
+
+Check the status of the container
+
+```bash
+$ db-middleware status
+```
+
+If the container is stopped, run `db-middleware start` command.
+
+<details>
+
+<summary>It shows something like this:</summary>
+
+```
+Config file loaded successfully.
+
++------------------------------+
+| Checking container status... |
++------------------------------+
+
+
++--------------------------------------------+
+| Database Middleware Status:                |
+|                                            |
+|                                            |
+| [Container]                                |
+|                                            |
+|   Name: con-db-middleware                  |
+|   Status: Up 11 minutes                    |
+|                                            |
+| [Performance]                              |
+|                                            |
+|   CPU Usage: 0.33%                         |
+|   Memory Usage: 62.27MiB / 3.63GiB (1.68%) |
+|   Block I/O: 0B / 0B                       |
+|   Network I/O: 6.34kB / 4.09kB             |
+|                                            |
+| [Network]                                  |
+|                                            |
+|   Network Mode: bridge                     |
+|   IP Address: 172.17.0.2                   |
+| 172.17.0.2                                 |
+|   Ports: 0.0.0.0:8080->8080/tcp            |
+|                                            |
+| [App]                                      |
+|                                            |
+|   Run Command: "bash /app/scripts/run.sh"  |
++--------------------------------------------+
+```
+
+</details>
+
 ---