docs: RHTAPBUGS-873 update doc about E2E tests (konflux-ci#816)

* RHTAPBUGS-873

* fix

README.md

@@ -158,7 +158,7 @@ For more information refer to [Generate Tests](docs/DeveloperGenerateTest.md).
 * When running via mage you can filter the suites run by specifying the
   `E2E_TEST_SUITE_LABEL` environment variable. For example:
   `E2E_TEST_SUITE_LABEL=ec ./mage runE2ETests`
-* `klog` level can be controled via `KLOG_VERBOSITY` environment variable. For
+* `klog` level can be controlled via `KLOG_VERBOSITY` environment variable. For
   example: `KLOG_VERBOSITY=9 ./mage runE2ETests` would output `curl` commands
   issued via Kubernetes client from sigs.k8s.io/controller-runtime
 
@@ -191,7 +191,7 @@ Our automated tests running in CI create lot of repositories in our redhat-appst
 
 There is a mage target that can cleanup those repositories - `mage local:cleanupGithubOrg`.
 
-For more infor & usage, please run `mage -h local:cleanupGithubOrg`.
+For more info & usage, please run `mage -h local:cleanupGithubOrg`.
 
 # PR review process in e2e-tests
 * Since RHTAP is leveraging OpenShift CI, [OWNERS](https://github.com/redhat-appstudio/e2e-tests/blob/main/OWNERS) file (in a directory or its parent directory) takes effect in e2e-tests PR review process. Reviewers are selected by [Blunderbuss plugin](https://github.com/kubernetes/test-infra/tree/master/prow/plugins/blunderbuss).
@@ -200,4 +200,4 @@ For more infor & usage, please run `mage -h local:cleanupGithubOrg`.
 
 * To get a PR merged, the following is needed:
   1. approved label added by selected [approver](https://github.com/kubernetes/community/blob/master/community-membership.md#approver) in relevant OWNERS file through [Blunderbuss plugin](https://github.com/kubernetes/test-infra/tree/master/prow/plugins/blunderbuss).
-  2. Tide check passed.
+  2. Tide check passed.

cmd/e2e_test.go

@@ -17,7 +17,7 @@ import (
 	_ "github.com/redhat-appstudio/e2e-tests/tests/integration-service"
 	_ "github.com/redhat-appstudio/e2e-tests/tests/release"
 	_ "github.com/redhat-appstudio/e2e-tests/tests/release/pipelines"
-	_ "github.com/redhat-appstudio/e2e-tests/tests/remotesecret"
+	_ "github.com/redhat-appstudio/e2e-tests/tests/remote-secret"
 	_ "github.com/redhat-appstudio/e2e-tests/tests/rhtap-demo"
 	_ "github.com/redhat-appstudio/e2e-tests/tests/spi"
 	_ "github.com/redhat-appstudio/e2e-tests/tests/upgrade"

docs/DeveloperGenerateTest.md

@@ -147,7 +147,7 @@ BuildSuiteDescribe: Build service E2E tests @build, @HACBS
 ## How it works
 
 We leverage existing Ginkgo's tool set to be able to do this translation back and forth. 
-* `ginkgo outline` we use to be able to generate the intial spec outline for our internal model based on what is in the file Ginkgo Test File. This command depends on the GoLang AST to generates the output. 
+* `ginkgo outline` we use to be able to generate the initial spec outline for our internal model based on what is in the file Ginkgo Test File. This command depends on the GoLang AST to generates the output. 
 * `ginkgo generate` we use to pass a customize template and data so that it can render a spec file using Ginkgo's extensive use of closures to allow us to build a descriptive spec hierarchy. 
 
 ## Schema

docs/InvestigatingCIFailures.md

@@ -35,7 +35,7 @@
            - This artifacts are present only with hypershift installer.
         - **redhat-appstudio_e2e-tests/gather-extra/**
            - Stores all cluster pods logs, events, configmaps etc. 
-           - This artifacts are present only when we dont use hypershift.
+           - This artifacts are present only when we don't use hypershift.
         - More details on all artifacts can be found in [OpenShift CI documentation](https://docs.ci.openshift.org/docs/how-tos/artifacts/ )
 
 ## Reporting and escalating CI Issue

pipelines/interrupt_catcher/README.md

@@ -20,7 +20,7 @@ oc create secret generic slack-token --from-literal="token=<TOKEN>"
 ```
 oc create secret generic slack-token --from-literal="token=<TOKEN>"
 ```
-* Deploy rest of the resoureces: 
+* Deploy rest of the resources: 
 ```
 cd pipelines/interrupt_catcher
 kubectl apply -f .

tests/README.md

@@ -5,9 +5,12 @@ Tests folder contains E2E related to several components divided in folders:
 | Folder | Component repository | README | Note |
 |---|---|---|---|
 | `build` | [build-service](https://github.com/redhat-appstudio/build-service), [jvm-build-service](https://github.com/redhat-appstudio/jvm-build-service) | [README.md](/tests/build/README.md) | |
-| `e2e-demos` | N/A | [README.md](/tests/e2e-demos/README.md) | |
-| `has` | https://github.com/redhat-appstudio/application-service | [README.md](/tests/has/README.md) | |
-| `integration-service` | https://github.com/redhat-appstudio/integration-service | [README.md](/tests/integration-service/README.md) |  |
+| `byoc` | [application-service](https://github.com/redhat-appstudio/application-service) | [README.md](/tests/byoc/README.md) | |
+| `enterprise-contract` | N/A | [README.md](/tests/enterprise-contract/README.md) | |
+| `integration-service` | [integration-service](https://github.com/redhat-appstudio/integration-service) | [README.md](/tests/integration-service/README.md) |  |
 | `load-tests` | N/A | [LoadTests.md](/docs/LoadTests.md) |  |
-| `release` | https://github.com/redhat-appstudio/release-service | [README.md](/tests/release/README.md) |  |
-| `spi` | https://github.com/redhat-appstudio/service-provider-integration-operator | [README.md](/tests/spi/README.md) | |
+| `release` | [release-service](https://github.com/redhat-appstudio/release-service) | [README.md](/tests/release/README.md) |  |
+| `remote-secret` | [remote-secret](https://github.com/redhat-appstudio/remote-secret) | [README.md](/tests/remote-secret/README.md) | |
+| `rhtap-demo` | N/A | [README.md](/tests/rhtap-demo/README.md) | |
+| `spi` | [service-provider-integration-operator](https://github.com/redhat-appstudio/service-provider-integration-operator) | [README.md](/tests/spi/README.md) | |
+| `upgrade` | N/A | [README.md](/tests/upgrade/README.md) | |

tests/release/pipelines/README.md

@@ -19,7 +19,7 @@ This suite contains e2e-tests for testing release pipelines from repository [rel
 ## How to Run tests:
 
 ### 1. To run all e2e-tests in suite ensure your changes of the suite tests are saved.
-- navigate to `e2e-tests` directoy 
+- navigate to `e2e-tests` directory 
  ```bash
  make build 
  ./bin/e2e-appstudio --ginkgo.junit-report=report.xml  --ginkgo.focus="pipelines"
@@ -31,7 +31,7 @@ This suite contains e2e-tests for testing release pipelines from repository [rel
 For example: 
 If a test has the label `label-test` to a test in suite `pipelines` then the test should run using the following arguments:
 
-- navigate to `e2e-tests` directoy 
+- navigate to `e2e-tests` directory 
  ```bash
  make build 
  ./bin/e2e-appstudio --ginkgo.junit-report=report.xml  --ginkgo.focus="pipelines" --ginkgo.label-filter="label-test"

tests/rhtap-demo/README.md

@@ -52,7 +52,7 @@ Steps to run 'rhtap-demos':
 
 ## Test Generator
 
-The test specs in e2e-demo-suite are generated dynamically using ginkgo specs.
+The test specs in rhtap-demo-suite are generated dynamically using ginkgo specs.
 
 If you want to test your own Component (repository), all you need to do is to update the `TestScenarios` variable in [scenarios.go](./config/scenarios.go)