circleci-smarter-testing-debugging
Installation
SKILL.md
CircleCI Smarter Testing Debugging
Explains test selection and test runs on a suite that is already onboarded. If .circleci/test-suites.yml doesn't exist, use circleci-smarter-testing-onboarding first.
Both commands are experimental — check circleci testsuite impact --help and circleci testsuite result --help if a flag below is rejected.
Run them from the project directory where tests are run. impact reads impact data from CircleCI, which needs circleci auth login; pass --local to read the impact data stored locally by --local runs instead.
Which command
| Question | Command |
|---|---|
| How were a job's test atoms selected, and how did they run? | circleci testsuite result <job-id> |
| Why did this test atom run or get skipped in that job? | circleci testsuite result <job-id> --test <atom> |
| Which test atoms were slowest in that job? | circleci testsuite result <job-id> --sort time |
| Which files impact this test atom? | circleci testsuite impact --test <atom> |
| Which test atoms does this file impact? | circleci testsuite impact --file <path> |
| Which files trigger the most tests? | circleci testsuite impact --sort impact |