github.com/redhat-appstudio/e2e-tests@v0.0.0-20230619105049-9a422b2094d7/tests/e2e-demos/README.md (about)

     1  # E2E DEMOS
     2  
     3  The e2e-demos suite contains a set of tests that covers AppStudio demos.
     4  
     5  Steps to run 'e2e-demos-suite':
     6  
     7  1) Follow the instructions from the [Readme](../../docs/Installation.md) scripts to install AppStudio in e2e mode
     8  2) Run the e2e suite: `./bin/e2e-appstudio --ginkgo.focus="e2e-demos-suite"`
     9  
    10  ## Test Generator
    11  
    12  The test specs in e2e-demo-suite are generated dynamically using ginkgo specs. To run the demo you need to use the default
    13  yaml located in `$ROOT_DIR/tests/e2e-demos/config/default.yaml`.
    14  
    15  Also it is possible to create your own yaml following the next structure:
    16  
    17  ```yaml
    18  tests: 
    19    - name: "create an application with nodejs component"
    20      applicationName: "e2e-nodejs"
    21      components:
    22        - name: "nodejs-component"
    23          type: "public"
    24          gitSourceUrl: "https://github.com/jduimovich/single-nodejs-app"
    25          devfileSource: "https://raw.githubusercontent.com/jduimovich/appstudio-e2e-demos/main/demos/single-nodejs-app/devfiles/devfile.yaml"
    26          language: "nodejs"
    27          healthz: "/"
    28          spec:
    29            replicas: 2
    30  ```
    31  
    32  To run the e2e-demos with a custom yaml use: `./bin/e2e-appstudio --ginkgo.focus="e2e-demos-suite" -config-suites=$PATH_TO_YOUR_CONFIG_YAML`
    33  
    34  ## Run tests with private component
    35  
    36  Red Hat AppStudio e2e framework now support to create components from private quay.io images and GitHub repositories.
    37  
    38  #### Environments
    39  
    40  | Variable | Required | Explanation | Default Value |
    41  |---|---|---|---|
    42  | `QUAY_OAUTH_USER` | yes | A quay.io username used to push/build containers  | ''  |
    43  | `QUAY_OAUTH_TOKEN` | yes | A quay.io token used to push/build containers. Note: the token and username must be a robot account with access to your repository | '' |
    44  
    45  #### Setup configuration for private repositories
    46  
    47  1. Define in your configuration file the application and the component
    48  Example of a github private repository:
    49  
    50  ```yaml
    51  tests: 
    52    - name: "RHDP-478: create an application with multiple components from private and public repositories"
    53      applicationName: "e2e-multiple-components"
    54      components:
    55        - name: "private-quarkus-component"
    56          type: "private"
    57          gitSourceUrl: "https://github.com/redhat-appstudio-qe/private-quarkus-devfile-sample"
    58          language: "quarkus"
    59          healthz: "/hello-resteasy"
    60  ```
    61  
    62  3. Run the e2e tests