Broken and stale unit tests #1812
-
I currently ran the unit tests on the project while I was fixing a bug and noticed that there's quite a number of broken unit tests. I'm considering contributing to resolving them if possible. I'll like to know if there's any reason the tests were left broken and if fixing the test is a good use of my time. Also, is there any consideration to migrate from karma to jest? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Hi, During the implementation of accessibility in v16, we had to rewrite many components, which left some tests invalid. Our goal for v18 is to strengthen the tests. We are grateful for your willingness to contribute. Contributions like these greatly help us advance PrimeNG. If you wish to submit a PR and make corrections, please feel free to do so. However, please submit a PR for one component first, and let's review it, don't forget to open an issue first and link the issue with the PR. You can also add some cases that we missed to extend the test coverage. Thanks in advance! |
Beta Was this translation helpful? Give feedback.
-
Hi all, We appreciate the effort and support received from you for broken tests to make PrimeNG better, you guys rock! |
Beta Was this translation helpful? Give feedback.
Hi,
During the implementation of accessibility in v16, we had to rewrite many components, which left some tests invalid. Our goal for v18 is to strengthen the tests. We are grateful for your willingness to contribute. Contributions like these greatly help us advance PrimeNG. If you wish to submit a PR and make corrections, please feel free to do so. However, please submit a PR for one component first, and let's review it, don't forget to open an issue first and link the issue with the PR. You can also add some cases that we missed to extend the test coverage.
Thanks in advance!