update: update README file with steps to run tests locally

Author: dhruvparekh12

README.md

@@ -8,8 +8,8 @@ With Launch CLI, you can interact with the Contentstack Launch platform using th
 * [Launch CLI plugin](#launch-cli-plugin)
 * [Installation steps](#installation-steps)
 * [Commands](#commands)
-* [How to test Changes Locally?](#how-to-test-changes-locally)
-* [Release & SRE Process:-](#release--sre-process-)
+* [How to do development Locally?](#how-to-do-development-locally)
+* [How to run tests Locally?](#how-to-run-tests-locally)
 <!-- tocstop -->
 
 # Installation steps
@@ -43,7 +43,7 @@ Run cloud functions locally
 
 
 
-# How to test Changes Locally?
+# How to do development Locally?
 - Branch out from development for development.
 - Install npm: @contentstack/cli 
 - Set region and log in using csdx config:set:region & csdx login
@@ -70,46 +70,14 @@ csdx <command-name>
 
 # How to run tests Locally?
 Step 1:- csdx config:set:region <region> Mentioned project should exists in provided org
-Step 2:- csdx login
-Step 3:- Create env on root level (refer: example.env file)
-Step 4:- run test cases (`npm run test:unit` or `npm run test:unit:report`)
-
-
-# Release & SRE Process:- 
-
-Version Increment:
-
-Patch version update (fixes): 1.0.0 → 1.0.1
-
-Minor version update (enhancements): 1.0.0 → 1.1.0
-
-Major version update (breaking changes): 1.0.0 → 2.0.0
-
-## For release:
 
-- Raise a draft pull request (PR) from the development branch to the main branch.
-
-### Pre-release SRE Preparation:
-
-- Create an SRE ticket a week before the release date, including the PR.
-
-- After the SRE review, address any identified issues and create tickets for any new issues. 
-
-- Request SRE approval if no issues are identified or after fixing all the SRE-raised issues.
-
-### CAB Approval:
-
-- For CAB, prepare deployment plan sheets(including publish & rollback plan).
-
-- Once SRE approves, raise the request for CAB(SRE ticket, deployment plan, release tickets, release notes). At least two CAB approvals are required.
+Step 2:- csdx login
 
-- Obtain approval for the PR from the security admin (Aravind) and launch admin.
+Step 3:- Create env on root level (refer: example.env file)
 
-### Merge and Release:
+Step 4:- run test cases (`npm run test:unit` or `npm run test:unit:report`)
 
-- After getting the necessary approvals, merge the PR. This will trigger the publishing process on npm and GitHub, which can be tracked through the actions & github released tags.
 
- 
 
 ### How will changes be reflected in the CLI ?
 If a patch or minor version of the launch is released, users will need to update or install the latest CLI version, which will automatically include the latest launch version.