-
Notifications
You must be signed in to change notification settings - Fork 45
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
Support for Japa testing framework #3276
Comments
@thetutlage - congrats on creating your own testing framework, it's no small feat. There's a lot of effort to add a new testing framework (not only initially but on an ongoing basis) so we need to be careful about adding support for new frameworks and ensure that there's widespread adoption to justify our effort. For now, we need to wait a bit and see how Japa adoption progresses. Please share this issue and have people +1 so we can gauge interest, and we will review in our periodic planning sessions. |
Hello @smcenlly I do see a few upvotes on this issue. No sure if they are enough to consider adding Japa as an option 😀. However, I would love to contribute myself, get it added and also advertise the integration in Japa docs. |
Thanks for reaching out. Unfortunately, from our perspective we still need to see more Japa adoption. Based on npm trends, Japa is currently about 50x less used than our least popular testing framework and 4000x less used than our most popular testing framework. To justify adding support for Japa, we'd need to see more use by the community. |
Alright. I think, I will close this issue in that case, because I don't see Japa reaching that mass adoption ever. Thanks for the quick reply :) |
Hello, I am the creator of Node.js testing framework called https://japa.dev/docs and would love to see it getting added to Wallabyjs.
Little bit about Japa 👇
node bin/test.js
. This file also acts as a mini CLI interface to filter tests, switch reporters and so on.Do let me know if you need anything else? Also happy to contribute in any possible way.
The text was updated successfully, but these errors were encountered: