updated README

Author: eishakaushal

__tests__/README.md

@@ -1,6 +1,10 @@
 # Testing 
 
 ### Preparation
+###
+### Frontend Testing
+
+For frontend testing, ensure you've prepared your environment as follows:
 
 1. React Testing Library versions 13+ require React v18. If your project uses an older version of React, be sure to install version 12
 ```
@@ -18,7 +22,7 @@ npm i @types/node
 npm install -D ts-node
 ```
 3. create jest.config.js 
-```
+```js
 module.exports = {
   verbose: true,
   setupFilesAfterEnv: ['./jest_setup/windowMock.js'],
@@ -34,13 +38,16 @@ module.exports = {
 };
 ```
 4. make sure jest_setup folder is at root directory of Chronos with styleMock.js and windowMock.js
-
+  ```js
   styleMock.js
   ```
+  ```js
   module.exports = {};
   ```
+  ```js
   windowMock.js
   ```
+  ```js
   // Mock window environment
   window.require = require;
 
@@ -50,9 +57,45 @@ module.exports = {
   // Mock get context
   HTMLCanvasElement.prototype.getContext = () => {};
   ```
-5. update database info inside test_settings.json 
+5. update database info inside `test_settings.json` 
 
 6. use `npm run test` to run jest tests
+###
+### Backend Testing
+
+For backend testing, ensure you've prepared your environment as follows:
+
+1. create `jest.config.js`
+```js
+module.exports = {
+  roots: ['<rootDir>'], // Set the root directory for test files (adjust this path to your test folder)
+  testRegex: '(/tests/.*|(\\.|/)(test|spec))\\.(jsx?|tsx?)$',
+  collectCoverage: true,
+  coverageDirectory: 'coverage',
+  testPathIgnorePatterns: ['/node_modules/', '/__tests__/'],
+};
+```
+2. install additional packages
+```
+npm i mongodb-memory-server
+```
+6. use `npm run backend-test` to run jest tests
+
+### End-to-End Testing
+
+Perform end-to-end testing with the following steps:
+
+1. install the following packages 
+```
+npm i selenium-webdriver
+npm i chromedriver
+```
+
+2. use `npm run dev:app` to start the app
+
+3. use `./node_modules/.bin/chromedriver` to run the Chromedriver executable
+
+4. use `npm run start:e2e` to run the end-to-end tests
 
 ## Contributing
 

chronos_npm_package/README.md

@@ -1,7 +1,7 @@
 ## What's New?
 - Enhanced Metrics Collection: Docker now supports Prometheus metrics scraping, offering improved monitoring capabilities
 - Streamlined Visualization: Docker and Kubernetes integrate with Grafana to provide dynamic visualization of collected metrics
-- Ability to select graph type and process kubernetes resource data
+- Kubernetes graph type customization and resource data processing 
 - Bug Fixes
 - Refactored code for additional modularity and customization
 
@@ -144,6 +144,7 @@ Chronos provides the option to send  emails. The properties that should be provi
 
 
 **NOTE: Email notification settings may require alternative security settings to work**
+#
 
 ### Chronos Tracker for "Microservices" Mode
 The mode `microservices` uses the additional setting `dockerized`, which indicates whether or not the microservice has been containerized with Docker. If omitted, Chronos will assume this server is not running in a container, i.e. `dockerized` will default to _false_. 
@@ -278,12 +279,13 @@ When viewing your information in the Chronos Electron application the data will
 
 **NOTE:** We provide a jmx_config.yaml file in the Chronos root folder for use with JMX prometheus that provides some useful baseline metrics to monitor.
 
-### Chronos Tracker for "docker" Mode
-Chronos can monitor Docker containers by saving metric data from instant queries to a Prometheus server in your Docker container. 
+#
+### Chronos Tracker for "Docker" Mode
+Chronos monitors Docker containers by storing metric data through instant Prometheus queries within your Docker container environment.
 
-In `chronos-config.js`, set the `mode` to `docker` and pass it both the name of the port the Prometheus server is listening on INSIDE the container, and the name of the Prometheus service so that its IP address can be resolved using DNS.
+In `chronos-config.js`, configure the `mode` parameter to `docker`. Additionally, provide the name of the port where the Prometheus server is actively listening inside the container, and specify the name of the Prometheus service to enable DNS-based resolution of its IP address.
 
-Also add a `grafanaAPIKey` section, this API key will grant chronos access to create and update dashboards in Grafana.
+Also add a `grafanaAPIKey` section, this API key will authorize Chronos for dashboard creation and updates in Grafana.
 
 ```js
 // Excerpt from a chronos-config.js
@@ -302,7 +304,7 @@ module.exports = {
 
 ```
 
-Then, insert the code below into a **SINGLE** microservice that will be deployed only as a **SINGLE** container, call `Chronos.docker`:
+Then, implement the subsequent code snippet within a **SINGLE** microservice that will be deployed only as a **SINGLE** container, and call `Chronos.docker`:
 
 ```js
 const chronosConfig = require('./chronos-config.js');
@@ -312,6 +314,7 @@ const chronos = new Chronos(chronosConfig);
 chronos.docker();
 ```
 
+
 ### Chronos Tracker for gRPC
 
 To monitor your gRPC server, setup `chronos-config.js` as if it was a standard microservices example, but be sure to set the `connection` type to `gRPC`.

examples/docker/README.md

@@ -27,11 +27,11 @@ For additional details on how Chronos works this example, please review the Dock
 
 ## Grafana API KEY
 
-1. Run docker compose command below (LN 61) to start your Grafana container before you can access your service account token.
+1. To initiate your Grafana container and prepare for accessing your service account token, execute the following command: `docker-compose -f docker-compose.yml up`
 
-2. In your browser, go to `localhost:32000`, which will be the login page of grafana. Use `admin` as both username and password to login. You can change the password after login.
+2. In your browser, go to `localhost:32000`, which will be the login page of Grafana. Use `admin` as both username and password to login. You can change the password after login.
 
-3. Navigate to `Home -> Administration -> Service accounts`, then click `Add service account` to create an service account. Be sure to choose `Admin` as the role. Then click `Add service account token`, hit `generate`, you are done! Remember this token, you will be using this token to access Grafana HTTP API programmatically.
+3. Navigate to `Home -> Administration -> Service accounts`, then click `Add service account` to create a service account. Be sure to choose `Admin` as the role. Then click `Add service account token`, hit `generate`, you are done! Remember this token, you will be using this token to access Grafana HTTP API programmatically.
 
 ## Steps to Run Example
 Peform the following steps in each of the _books_, _customers_, _frontend_, and _orders_ directories
@@ -55,7 +55,7 @@ CHRONOS_GRAFANA_API_KEY = Bearer [the access token you created in above section
 
     - If you have the dependency as `"@chronosmicro/tracker": "file:./chronos_npm_package"`, which is a **local** file, make sure to change the version from `"file:./chronos_npm_package"` to `"^12.0.1"` and run npm install.  **Unless you are wanting to test local copies of the "Chronos_npm_package" file**
 
-3.  With the terminal navigated to the the _examples/docker_ folder, run the command:
+3.  With the terminal navigated to the _examples/docker_ folder, run the command:
 
 ```
 docker-compose -f docker-compose.yml up