Scaling Unit tests with NX #5421
joshlperry
started this conversation in
General
Replies: 2 comments 4 replies
-
Either make more granular shared libraries or I think you have to live with this. |
Beta Was this translation helpful? Give feedback.
3 replies
-
I have kind of the same problem, and I think about refactoring the structure of my apps and libs. Are there any tools/generators/schematics for that kind of thing? like
.. or just something to get a component/class based graph within the lib and usages of outside the lib? more granular than app/lib dependencies? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As the amount of applications has grown in our NX repo, containing a shared components library. When updating a shared component this is triggering at least 8 projects from 'nx affected:apps' to start running unit tests resulting in a growing issue of increased time to test (40+ minutes on the pipeline). We have looked into 'jest --onlyChanged' which is supported by NX however we'd like a solution that would run tests in our applications that use that shared component.
How do we better specify what tests to run?
Curious to see what options we have.
Beta Was this translation helpful? Give feedback.
All reactions