remove redundant parameters that can be done by using CC_TESTS env var

Author: manolo

README.md

@@ -1,12 +1,3 @@
-# [Platform-In-Test Script]
-
-# How To Use
-
-```
-./scripts/pit/run.sh --help
-```
-
-```
 Use: ./scripts/pit/run.sh with the next options:
 
  --version=string  Vaadin version to test, if not given it only tests current stable, otherwise it runs tests against current stable and then against given version.
@@ -24,8 +15,6 @@ Use: ./scripts/pit/run.sh with the next options:
  --skip-dev        Skip dev-mode validations
  --skip-clean      Do not clean maven cache
  --skip-helm       Do not re-install control-center with helm and continue running tests, implies (--offline, --keep-cc)
- --skip-setup      Like --skip-helm but also do not run first playwright setup test, implies --skip-build --skip-helm
- --skip-apps       Like --skip-setup but also do not run playwright install apps test, implies --skip-build --skip-setup
  --skip-pw         Do not run playwright tests
  --cluster=name    Run tests in an existing k8s cluster
  --vendor=name     Use a specific cluster vendor to run control-center tests options: [dd, kind, do] (default: kind)
@@ -117,8 +106,4 @@ Use: ./scripts/pit/run.sh with the next options:
                    · designer-tutorial
                    · walking-skeleton:v24.7-hybrid
                    · releases-graph
-                   · expo-flow
-```
-
-
-
+                   · expo-flow

scripts/pit/lib/lib-args.sh

@@ -22,8 +22,6 @@ Use: $0 with the next options:
  --skip-dev        Skip dev-mode validations
  --skip-clean      Do not clean maven cache
  --skip-helm       Do not re-install control-center with helm and continue running tests, implies (--offline, --keep-cc)
- --skip-setup      Like --skip-helm but also do not run first playwright setup test, implies --skip-build --skip-helm
- --skip-apps       Like --skip-setup but also do not run playwright install apps test, implies --skip-build --skip-setup
  --skip-pw         Do not run playwright tests
  --cluster=name    Run tests in an existing k8s cluster
  --vendor=name     Use a specific cluster vendor to run control-center tests options: [dd, kind, do] (default: kind)
@@ -95,8 +93,6 @@ checkArgs() {
       --keep-apps) KEEPAPPS=true;;
       --skip-build) SKIPBUILD=true;;
       --skip-helm)  OFFLINE=true; KEEPCC=true; SKIPHELM=true ;;
-      --skip-setup) OFFLINE=true; KEEPCC=true; SKIPHELM=true; SKIPBUILD=true; SKIPSETUP=true;;
-      --skip-apps)  OFFLINE=true; KEEPCC=true; SKIPHELM=true; SKIPSETUP=true; SKIPBUILD=true; SKIPAPPS=true ;;
       --pnpm) PNPM="-Dpnpm.enable=true";;
       --vite) VITE=true;;
       --list*)

scripts/pit/lib/lib-k8s-cc.sh

@@ -261,9 +261,6 @@ runPwTests() {
   [ "$2" = local -a "$VENDOR" = do ] && R=$DO_REG_URL && S="--secret=$DO_REGST"
 
   for f in $CC_TESTS; do
-    [ -n "$SKIPSETUP" -a `basename $f` = "cc-setup.js" ] && continue
-    [ -n "$SKIPAPPS"  -a `basename $f` = "cc-install-apps.js" ] && continue
-    [ -n "$KEEPAPPS"  -a `basename $f` = "cc-remove-apps.js" ] && continue
     [ "$CLUSTER" == "docker-desktop" ] || stopForwardIngress && forwardIngress $CC_NS || return 1
     runPlaywrightTests "$PIT_SCR_FOLDER/its/$f" "" "$T" "control-center" \
       --url=https://$CC_CONTROL --login=$CC_EMAIL --version=$CCVERSION \