You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As our test suite has grown to over 100 tests, we need to consider our approach to testing in order to maintain our development agility. While comprehensive testing is essential, it's crucial to balance thoroughness with efficiency. I propose that we temporarily reduce the scope of our test coverage while maintaining our current level of documentation and examples. This will allow us to focus on adding new functionality without sacrificing code quality. We can always revisit and expand our test coverage as needed. Additionally, I encourage us to continuously improve our documentation, as demonstrated in one of our current pull request.
The text was updated successfully, but these errors were encountered:
Proposed new feature or change:
As our test suite has grown to over 100 tests, we need to consider our approach to testing in order to maintain our development agility. While comprehensive testing is essential, it's crucial to balance thoroughness with efficiency. I propose that we temporarily reduce the scope of our test coverage while maintaining our current level of documentation and examples. This will allow us to focus on adding new functionality without sacrificing code quality. We can always revisit and expand our test coverage as needed. Additionally, I encourage us to continuously improve our documentation, as demonstrated in one of our current pull request.
The text was updated successfully, but these errors were encountered: