Skip to main content
Version: 0.8.0

How to Run Frontend Integration Test


  • The test cases under the directory test-e2e are integration tests to ensure the correctness of the Submarine Workbench.

  • These test cases can be run either locally or on GitHub Actions.

Run E2E test locally

  1. Ensure you have setup the submarine locally. If not, you can refer to Quickstart.

  2. Forward port

    kubectl port-forward --address service/submarine-traefik 32080:80
  3. Modify

    You need to modify the port and the URL in this script to where you run the workbench on.

    Example: If your Submarine workbench is running on, you should modify the WORKBENCH_PORT to 4200.

    # at submarine-test/test_e2e/
    # ======= Modifiable Variables ======= #
    # Note: URL must start with "http"
    # (Ref:
    WORKBENCH_PORT=8080 #<= modify this
    URL="" #<=modify this
    # ==================================== #
  4. Run (Run a specific test case)

    This script will check whether the port can be accessed or not, and run the test case.

    # at submarine-test/test_e2e
    ./ ${TESTCASE}
    # TESTCASE is the IT you want to run, ex: loginIT, experimentIT...
  5. Run all test cases

  • Following commands will compile all files and run all files ending with "IT" in the directory.

    # Make sure the Submarine workbench is running on
    cd submarine/submarine-test/test-e2e
    # Method 1:
    mvn verify

    # Method 2:
    mvn clean install -U

Run E2E test in GitHub Actions

  • Each time a commit is pushed, GitHub Actions will be triggered automatically.

Add a new frontend E2E test case

    • You MUST read the document carefully, and understand the difference between explicit wait, implicit wait, and fluent wait.
    • Do not mix implicit and explicit waits. Doing so can cause unpredictable wait times.
  • We define many useful functions in