mirror of
https://github.com/larksuite/cli.git
synced 2026-09-14 18:42:53 +08:00
yballul-bytedance
5a54bc07db
Form submission writes and submits data through a public share link, an irreversible action that should require explicit confirmation. Reclassify the shortcut from write to high-risk-write so the runner's --yes gate fires before execution, matching +form-delete and other high-risk base commands. Update the lark-base skill docs (--yes on all examples, param table, tips) and add tests pinning the confirmation gate (unit) and dry-run structure (e2e). Co-authored-by: yballul-bytedance <273011618+yballul-bytedance@users.noreply.github.com>
CLI E2E Tests
This directory contains end-to-end tests for lark-cli.
The purpose of this module is to verify real CLI workflows from a user-facing perspective: run the compiled binary, execute commands end to end, and catch regressions that are not obvious from unit tests alone.
What Is Here
core.go,core_test.go: the shared E2E test harness and its own testsdemo/: reference testcase(s)cli-e2e-testcase-writer/: the local skill for adding or updating testcase files in this module
For Contributors
When writing or updating testcases under tests/cli_e2e, install and use this skill first:
npx skills add ./tests/cli_e2e/cli-e2e-testcase-writer
Then follow tests/cli_e2e/cli-e2e-testcase-writer/SKILL.md.
Example prompt:
Use $cli-e2e-testcase-writer to write lark-cli xxx domain related testcases.
Put them under tests/cli_e2e/xxx.
Run
make build
go test ./tests/cli_e2e/... -count=1