Use Playwright instead of testIM (#596)

* Use Playwright instead of testIM

Author: sgalsaleh

.github/actions/e2e/action.yml

@@ -19,12 +19,6 @@ inputs:
   license:
     description: 'license (b64) to use for e2e tests'
     required: true
-  testim-access-token:
-    description: 'testim access token'
-    required: true
-  testim-branch:
-    description: 'testim branch'
-    required: true
   dr-aws-access-key-id:
     description: 'Disaster Recovery AWS Access Key ID'
     required: true
@@ -90,8 +84,6 @@ runs:
       export SNAPSHOT_LICENSE_ID=${{ inputs.snapshot-license-id }}
       echo "${{ inputs.license }}" | base64 --decode > e2e/license.yaml
       echo "${{ inputs.snapshot-license }}" | base64 --decode > e2e/snapshot-license.yaml
-      export TESTIM_ACCESS_TOKEN=${{ inputs.testim-access-token }}
-      export TESTIM_BRANCH=${{ inputs.testim-branch }}
       export DR_AWS_S3_ENDPOINT=https://s3.amazonaws.com
       export DR_AWS_S3_REGION=us-east-1
       export DR_AWS_S3_BUCKET=kots-testim-snapshots
@@ -103,20 +95,20 @@ runs:
     uses: actions/upload-artifact@v4
     if: ${{ failure() }}
     with:
-      name: ${{ github.job }}-support-bundle-host.tar.gz
+      name: ${{ inputs.test-name }}-support-bundle-host.tar.gz
       path: ./e2e/support-bundle-host.tar.gz
   - name: Upload Cluster Support Bundle
     uses: actions/upload-artifact@v4
     if: ${{ failure() }}
     with:
-      name: ${{ github.job }}-support-bundle-cluster.tar.gz
+      name: ${{ inputs.test-name }}-support-bundle-cluster.tar.gz
       path: ./e2e/support-bundle-cluster.tar.gz
   - name: Upload Playwright Report
     id: upload-playwright-report
     uses: actions/upload-artifact@v4
     if: ${{ failure() }}
     with:
-      name: ${{ github.job }}-playwright-report.tar.gz
+      name: ${{ inputs.test-name }}-playwright-report.tar.gz
       path: ./e2e/playwright-report.tar.gz
   - name: Print instructions to view Playwright report
     if: ${{ failure() && steps.upload-playwright-report.outputs.artifact-url != '' }}

.github/workflows/pull-request.yaml

@@ -204,8 +204,6 @@ jobs:
         snapshot-license: ${{ secrets.STAGING_EMBEDDED_CLUSTER_SNAPSHOT_LICENSE }}
         license-id: ${{ secrets.STAGING_EMBEDDED_CLUSTER_LICENSE_ID }}
         license: ${{ secrets.STAGING_EMBEDDED_CLUSTER_LICENSE }}
-        testim-access-token: ${{ secrets.TESTIM_ACCESS_TOKEN }}
-        testim-branch: ${{ github.head_ref == 'main' && 'master' || github.head_ref }}
         dr-aws-access-key-id: ${{ secrets.TESTIM_AWS_ACCESS_KEY_ID }}
         dr-aws-secret-access-key: ${{ secrets.TESTIM_AWS_SECRET_ACCESS_KEY }}
 

.github/workflows/release-dev.yaml

@@ -156,7 +156,5 @@ jobs:
           snapshot-license: ${{ secrets.STAGING_EMBEDDED_CLUSTER_SNAPSHOT_LICENSE }}
           license-id: ${{ secrets.STAGING_EMBEDDED_CLUSTER_LICENSE_ID }}
           license: ${{ secrets.STAGING_EMBEDDED_CLUSTER_LICENSE }}
-          testim-access-token: ${{ secrets.TESTIM_ACCESS_TOKEN }}
-          testim-branch: 'master'
           dr-aws-access-key-id: ${{ secrets.TESTIM_AWS_ACCESS_KEY_ID }}
           dr-aws-secret-access-key: ${{ secrets.TESTIM_AWS_SECRET_ACCESS_KEY }}

e2e/README.md

@@ -67,20 +67,9 @@ Make sure to update the application yaml files under kots-release-onmerge
 and kots-release-onpr directories if you create a new release of the remote
 application.
 
-### Testim
+### Playwright
 
-We use [Testim](https://www.testim.io/) to run end to end tests on the UI. The tests live within the
-"Embedded Cluster" Testim project.
+We use [Playwright](https://playwright.dev/) to run end to end tests on the UI.
+The tests live in the `playwright` directory.
 
-When a git branch is pushed to GitHub, a cooresponding branch is created in
-Testim. The on-PR tests will run against the matching branch in Testim, so if you need
-to make changes to the tests as part of your PR, you should make those updates in your
-Testim branch.
-
-When a PR is merged, the on-merge tests will run against the master branch in Testim.
-If you have made changes to the tests in your Testim branch, you should merge those changes
-to the master branch in Testim when merging your PR. Similarly, if you rebase your git
-branch from main, you may need to "rebase" your Testim branch (merge changes from master)
-if there have been changes to the tests.
-
-For more details on version control in Testim, refer to the [Testim documentation](https://help.testim.io/docs/version-control-branches).
+For more details on how to write tests with Playwright, refer to the [Playwright documentation](https://playwright.dev/docs/writing-tests).