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
I've introduced a general facility for unit testing as part of #841 which makes it practical to write individual unit tests for BBB implementation methods. I just want to lay down some rules right away though in case anyone is suddenly inspired to start cranking out unit tests.
The facility is still immature and some abstractions are not probably optimal or adequate, so please bear that in mind.
Do not send PRs with hundreds of new tests at this time. We want to start small and only scale up our tests once the tests and the supporting facilities are proven to be fast, easy to use, and easy to maintain. If tests are not maintainable or break easily due to refactoring, I will likely start ripping them out. So please start small with just a couple tests at a time to start.
Here are some rules about tests in general:
⚠️ Tests which significantly add to build time or break easily due to unrelated refactors very likely will not be merged or may be reverted.
⚠️ Tests which cannot be easily run individually will not be merged. Please either stick to one (well-named) method per test, or provide documentation as to how to run tests individually with your PR.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've introduced a general facility for unit testing as part of #841 which makes it practical to write individual unit tests for BBB implementation methods. I just want to lay down some rules right away though in case anyone is suddenly inspired to start cranking out unit tests.
Here are some rules about tests in general:
Beta Was this translation helpful? Give feedback.
All reactions