@mallardbay/cursor-rules 1.0.26 → 1.0.27
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -12,7 +12,7 @@ We aim for high-impact test coverage, focused on adding value and improving deve
|
|
|
12
12
|
|
|
13
13
|
We do not chase 100% coverage for its own sake. If a test doesn’t meaningfully reduce risk or help developers move faster, it’s not worth writing. The goal is smart coverage, not maximum coverage—optimize for reliability, clarity, and development speed without overengineering.
|
|
14
14
|
|
|
15
|
-
Avoid e2e tests for UI. Favor unit tests.
|
|
15
|
+
**Frontend (React, React Native):** Avoid e2e tests for UI. Favor unit tests. **Backend (Node.js):** Prioritize e2e tests.
|
|
16
16
|
|
|
17
17
|
### Coverage Requirements
|
|
18
18
|
|
|
@@ -12,7 +12,7 @@ We aim for high-impact test coverage, focused on adding value and improving deve
|
|
|
12
12
|
|
|
13
13
|
We do not chase 100% coverage for its own sake. If a test doesn’t meaningfully reduce risk or help developers move faster, it’s not worth writing. The goal is smart coverage, not maximum coverage—optimize for reliability, clarity, and development speed without overengineering.
|
|
14
14
|
|
|
15
|
-
Avoid e2e tests for UI. Favor unit tests.
|
|
15
|
+
**Frontend (React, React Native):** Avoid e2e tests for UI. Favor unit tests. **Backend (Node.js):** Prioritize e2e tests.
|
|
16
16
|
|
|
17
17
|
### Coverage Requirements
|
|
18
18
|
|