mirror of
https://github.com/larksuite/cli.git
synced 2026-07-07 00:55:53 +08:00
* feat: add stable bot-only cli e2e subset Change-Id: I62edf59d179e407954f65f82e94cf5dcf4938080 * fix: address review comments on stable cli e2e tests Change-Id: I4436100c30adf2694cd06953961f8d77f576fc1e * fix: reduce flakiness in drive and im e2e helpers Change-Id: I51e77d857f1fd9aec5ee34adf5045cc695239f21 * fix: document missing drive cleanup support Change-Id: I3d4f034145bd69fb7640e707fcda05146b8754c7 * style: unify e2e cleanup comments Change-Id: I40d906c9168754ad71ef9fb770ff4c340fc19beb * test: update e2e assertions Change-Id: I73c21b4b38d4ced7ea27cb327075957ec2b9a2a2 * test: stabilize cli e2e bot-only coverage Change-Id: Ied897c37c4f42e446d55d110461aa34ae198195d
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