-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port home-grown test framework to Busted #356
Comments
I've had this thought many times, but lacked the time. So fwiw please go ahead
that's over-engineering imho, but doesn't hurt either |
I think we can close this now? the whole thing will be a work in progress for a while |
Yes. The basics are in place and all new tests should be in Busted. Legacy ones can continue to be ported as we get a chance to refactor them. |
@Tieske, @hishamhm —
How would you guys feel about it if I were to port all the current tests from the current in-project test runner to Busted? This would not add a runtime dependency, but it would be an extra build / test / developer dependency.
The issues I have with the current system are that...
pcall()
wrappers, but Busted's expectations for error messages and various conditions are quite a bit more robust.$(nproc)
× faster if it was easier to run them in parallel. The current framework makes that tricky. Busted doesn't have this built in (yet) either, but the different output options make it much easier to execute from something that does support job control (GNU parallel, GNU Make's test harnesses, etc.)I make no promise to get around to this right away as it would take a bit of doing, but I thought I'd ask whether such a thing would be acceptable before I get started.
The text was updated successfully, but these errors were encountered: