-
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
idea: WaaS #675
Comments
Initially wallaby.js was planned as a cloud based runner. After a few experiments and analysis, it was decided to start with a client side tool, but to write in in way that it may be possible to host in a cloud in future. We have cut a few corners since then (like using locally installed node modules and not re-installing or copying them to wallaby cache), but managed to more or less keep the possible option to host wallaby core anywhere, not just on the developer's machine. Building a cloud infrastructure to host wallaby is clearly a large chunk of work, with all the known problems you have listed and more. Building a nicer UI for displaying various test results is a problem that can be tackled independently (as you also mentioned). And as a matter of fact, we are doing it right now - there'll be multiple tabs apart from the Test Explorer, like Coverage, Config, possibly license management, etc.
Could you please share what kind of graphs and visual feedback you'd like to see? |
Just brainstorming here.
|
@boneskull Thanks for sharing the ideas! I like them all, please keep posting if you have more over time. Configuration assistant/wizard, plus something to increase the transparency of what wallaby.js is doing behind the scenes (like displaying compilation/preprocessing steps and intermediate results) is definitely something that I think we should prioritise. Proper debugger support is also on the roadmap, though I think it's something that would be much better if implemented right inside the editor. |
Yeah I want |
+1 for Test coverage as a pie. |
+1 for:
we have a build script that fails the build if you trend down from previous build, it will help immensely if a time-series is displayed, even a simple line plot. BTW you should open-source the wallaby.app guys, that way the community can help with a lot of those enhancements. It's not like it's your core product anyway... |
@ivankolev Thanks for your feedback!
We are discussing this possibility internally. |
This might be far-fetched. What if Wallaby provided a cloud service which would run tests instantaneously? Kind of like instant CI.
A couple advantages:
Immediately known problems:
However! This doesn't have to run in the cloud. Wallaby could show all sorts great info if it launched your browser and streamed data while you were working (a la Karma, except with an actual GUI). Real-time graphs, better visual feedback. It could help address some of the problems I mentioned in #674 by displaying several "contexts" at once.
The text was updated successfully, but these errors were encountered: