test: the platform test covers what the CLI manages, not only runs

.github/workflows/platform-e2e.yml

@@ -1,8 +1,8 @@
 name: Platform E2E
 
 # Uses the CLI against the dev platform the way a pipeline does (e2e/platform.sh), with
-# the team token of the test team CLI-E2E. Only wait steps, and everything it creates is
-# deleted afterwards.
+# the team token of the test team CLI-E2E, then the rest of what the CLI covers, partly
+# with an admin token. Only wait steps, and everything it creates is deleted afterwards.
 on:
   # Weekly, Tuesday evening, so a change on the platform side shows within a week. Cron
   # is UTC: 19:00 in Berlin in summer, 18:00 in winter.
@@ -34,6 +34,7 @@ jobs:
     env:
       STEADYBIT_URL: https://platform.dev.steadybit.com
       STEADYBIT_TOKEN: ${{ secrets.STEADYBIT_E2E_TOKEN }}
+      STEADYBIT_E2E_ADMIN_TOKEN: ${{ secrets.STEADYBIT_E2E_ADMIN_TOKEN }}
       STEADYBIT_E2E_TEAM: CLI
       STEADYBIT_E2E_ENVIRONMENT: Global
     steps:

CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## v6.2.2
+
+- `execution property set` with a single `--value` sets a list property, such as a
+  `STRING_LIST`, to a list of that one value; the platform refused it with "must be a
+  list of strings". Found by the platform test, which now covers templates, run
+  properties, schedules, services, environments, teams, access tokens, hubs and
+  integrations.
+
 ## v6.2.1
 
 - `--expect-state RUNNING` (or `PREPARED`, `CREATED`) passes for a run that ended after it

CONTRIBUTING.md

@@ -69,13 +69,18 @@ docker run --rm -v "$PWD/e2e:/e2e" --entrypoint sh steadybit/cli:under-test /e2e
 The platform test uses the released CLI the way a pipeline does, against the dev
 platform with the team token of the test team CLI-E2E (key `CLI`): experiments applied
 from files, run in parallel with a report, checked for drift, canceled by SIGTERM,
-refused while another runs, and found by an `execution list` gate. It only uses wait
-steps and deletes what it creates. CI runs it weekly, after each stable release, and on
-pull requests that change it; a nightly job only checks that the token and the API
-still work. To run it by hand, with `steadybit` on the `PATH`:
+refused while another runs, and found by an `execution list` gate. Then the rest of
+the platform the CLI covers: templates, run properties, schedules, services and service
+profiles with the team token, and environments, teams, access tokens, hubs,
+integrations and the audit log with an admin token. It only uses wait steps, and deletes
+what it creates, which is named `cli-e2e-ci-*`. It only reads the kill switch and sends
+no invitation. CI runs it weekly, after each stable release, and on pull requests that
+change it; a nightly job only checks that the token and the API still work. To run it by
+hand, with `steadybit` on the `PATH` (without the admin token, those checks are skipped):
 
 ```sh
-STEADYBIT_URL=https://platform.dev.steadybit.com STEADYBIT_TOKEN=<token of team CLI> e2e/platform.sh
+STEADYBIT_URL=https://platform.dev.steadybit.com STEADYBIT_TOKEN=<token of team CLI> \
+  STEADYBIT_E2E_ADMIN_TOKEN=<admin token> e2e/platform.sh
 ```
 
 ### Output compatibility