From 92f18b72b84b88cff46e4d3d0bd8d4b1a3b0b141 Mon Sep 17 00:00:00 2001 From: Paul Kuruvilla Date: Thu, 25 Sep 2025 23:30:44 -0700 Subject: [PATCH] docs: improve development workflow linting and testing guidelines Update the development workflow documentation to clarify the linting and testing process. Advise running `npm run lint` after making changes and only running tests selectively using `npx run ember test` with module names, instead of using slow commands like `npm test` or `npm run test`. Provide guidance on finding the module name in test files or asking for help when unsure. --- .cursor/rules/development-workflow.mdc | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/.cursor/rules/development-workflow.mdc b/.cursor/rules/development-workflow.mdc index cf82bdf7db..4bd393818f 100644 --- a/.cursor/rules/development-workflow.mdc +++ b/.cursor/rules/development-workflow.mdc @@ -5,6 +5,11 @@ alwaysApply: true When you're asked to make changes, follow these rules: - Say consistent with the rest of our codebase. Read other files to understand what our patterns are. -- Don't run tests using `npm test`, those are extremely slow. Just use `npm run lint` instead. +- Run `npm run lint` after making changes. +- Once linting is successful, you can try running tests if there are ones that cover the area you changed. + - Use `npx run ember test --module ''` to run tests. + - If you know the test file, the module name is at the top (`module('...', function (hooks) { ... })`) + - If you're unsure about the test file, ask me. +- Don't run `npm run test`, that's super slow. - Don't run commands like `npm run build` / `npm run start`.