Skip to content

docs: improve development workflow linting and testing guidelines #3127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rohitpaulk merged 1 commit into from
Sep 26, 2025
Merged

docs: improve development workflow linting and testing guidelines #3127

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion .cursor/rules/development-workflow.mdc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 '<module-name>'` 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`.