Drop the environment switch in dev and test, and update gs (#2754)

alibaba · May 26, 2023 · 747df41 · 747df41
1 parent 46d7ed8
commit 747df41
Show file tree

Hide file tree

Showing 2 changed files with 131 additions and 150 deletions.
diff --git a/docs/development/how_to_test.md b/docs/development/how_to_test.md
@@ -33,19 +33,8 @@ With `gs` command-line utility, you can build all targets for GraphScope with a
 ### Run tests
 
 Run a bunch of test cases that involves 3 engines
-
-````{note}
-`gs` could let you easily switch from production mode and development mode, where
-
-- production mode means you have installed graphscope to somewhere and you want to use the executable located at there.
-- development mode means you want to find your executables in local directory
-
-For example, execute `export GRAPHSCOPE_ENV=prod` to set working directory to `/opt/graphscope` (the default GRAPHSCOPE_HOME location), and execute `export GRAPHSCOPE_ENV=dev` will set working directory to your local GraphScope repository.
-````
-
 ```bash
-export GRAPHSCOPE_ENV=prod
-./gs test local-e2e
+./gs test e2e --local
 ```
 
 ## Test GraphScope on Kubernetes cluster
@@ -90,5 +79,5 @@ The tests would launch a couple of pods on your cluster, so you need to set appr
 Take our previous built image for example, which has an empty registry (or you could say it's `docker.io` by default), and tagged `latest`
 
 ```bash
-./gs test k8s-e2e --registry="" --tag="latest"
+./gs test e2e --k8s --registry="docker.io" --tag="latest"
 ```