Update readme for e2e (#2496)

kafka-ui-e2e-checks/README.md

@@ -45,58 +45,20 @@ docker pull selenoid/vnc:chrome_86.0
 
 ### How to run checks
 
-1. Run `kafka-ui` 
+1. Run `kafka-ui`: 
 ```
-cd docker
-docker-compose -f kafka-ui.yaml up -d
+cd kafka-ui
+docker-compose -f documentation/compose/kafka-ui-connectors.yaml up -d
 ```
-2. Run `selenoid-ui` 
+2. Run tests using your QaseIO API token as environment variable (put instead $s into command below)
 ```
-cd kafka-ui-e2e-checks/docker
-docker-compose -f selenoid.yaml up -d
+mvn -DQASEIO_API_TOKEN=‘%s’ -pl ‘!kafka-ui-api’ test -Pprod
 ```
-3. Compile `kafka-ui-contract` project
-```
-cd <projectRoot>/kafka-ui-contract
-mvn clean compile
-```
-4. Run checks 
-```
-cd kafka-ui-e2e-checks
-mvn test
-```
-
-* There are several ways to run checks
-
-1. If you don't have  selenoid run on your machine
-```
- mvn test -DSHOULD_START_SELENOID=true
-```
-⚠️ If you want to run checks in IDE with this approach, you'd need to set up
-environment variable(`SHOULD_START_SELENOID=true`) in `Run/Edit Configurations..`
-
-2. For development purposes it is better to just start separate selenoid in docker-compose
-Do it in separate window
-```
-cd docker
-docker-compose -f selenoid.yaml up
-```
-Then you can just `mvn test`. By default, `SELENOID_URL` will resolve to `http://localhost:4444/wd/hub`
-
-It's preferred way to run. 
-
-* If you have remote selenoid instance, set 
-
-`SELENOID_URL` environment variable
-
-Example:
-`mvn test -DSELENOID_URL=http://localhost:4444/wd/hub`
-That's the way to run tests in CI with selenoid set up somewhere in cloud
 
 ### Reporting
 
 Reports are in `allure-results` folder.
-If you have installed allure commandline(e.g. like [here](https://docs.qameta.io/allure/#_installing_a_commandline) or [here](https://www.npmjs.com/package/allure-commandline))
+If you have installed allure commandline [here](https://www.npmjs.com/package/allure-commandline))
 You can see allure report with command:
 ```
 allure serve