[GitHub] [submarine] kevin85421 opened a new pull request #590: SUBMARINE-836. Frontend E2E test for Submarine Operator

[GitBox]

kevin85421 opened a new pull request #590:
URL: https://github.com/apache/submarine/pull/590


   ### What is this PR for?
   To make sure of the correctness of Submarine Operator, a helper script to 
execute the frontend E2E test is necessary.
   
   ### What type of PR is it?
   [Feature]
   
   ### Todos
   * Survey unstable testcases (sidebarIT, departmentIT, loginIT, notebookIT, 
environmentIT)
     * Start from departmentIT
   * Improve the flexibility of E2E test framework (ex: Make the port in 
run_frontend_e2e.sh modifiable.)
   * Update 
[IntegrationTest.md](https://github.com/apache/submarine/blob/master/website/docs/devDocs/IntegrationTest.md)
   * Testcases for experiment page are not enough
   
   
   ### What is the Jira issue?
   https://issues.apache.org/jira/browse/SUBMARINE-836
   
   ### How should this be tested?
   ```
   # Step1: Build & Run submarine operator (out-of-cluster)
   go build -o submarine-operator
   ./submarine-operator
   
   # Step2: Create a Custom Resource
   kubectl create ns submarine-operator-test
   kubectl apply -n submarine-operator-test -f 
artifacts/examples/example-submarine.yaml
   
   # Step3: Check Cluster status (Until every resource is ready)
   kubectl get all -n submarine-user-test
   
   # Step4: Check Workbench (127.0.0.1:8080)
   
   # Step5: Run a frontend E2E testcase
   #             Usage: ./hack/run_frontend_e2e.sh [testcase]
   #             [testcase]: Check the directory 
"submarine-test/test-e2e/src/test/java/org/apache/submarine/integration"
   ./hack/run_frontend_e2e.sh loginIT
   ```
   
   ### Screenshots (if appropriate)
   
   
https://user-images.githubusercontent.com/20109646/119352359-2a146380-bcd4-11eb-825f-1492328f03c3.mov
   
   
   <img width="953" alt="截圖 2021-05-24 下午9 07 52" 
src="https://user-images.githubusercontent.com/20109646/119352331-1ff26500-bcd4-11eb-9540-043ee47b3747.png";>
   
   
   ### Questions:
   * Do the license files need updating? No
   * Are there breaking changes for older versions? No
   * Does this need new documentation? No
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org