-
Notifications
You must be signed in to change notification settings - Fork 121
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
[Enhancement] Support for "full stack" debug and automated acceptance testing #61
Comments
@fizxmike , first I am glad you have been abble to prototype an application with Neutronium. I will be great if you can share information about it once it is finalized. Thanks for your suggestion about Neutronium tests/debugs: tooling is an import part of neutronium.
|
My prototype is big enough now that any new feature or re-factor I do, I spend more and more time manually checking that nothing has broken. I need to get automated testing figured out very soon.
Of course, the "holy grail" would be automated "full stack" tests, which relies on item 1 above. The method I tried in my first post might work... it really depends on the behavior of the test runner (whether or not it triggers window.location.reload() or not). I'll let you know more when I find out. |
Provided in version 1.3.0 |
Hi,
Now that I've hit a stride with Neutronium and created a working SPA prototype, I'm thinking long an hard about automated testing. Unit test are easy (either testing ViewModel in C#, or Vue.js components with a JS test runner using mocks of vm.cjson).
But, what I really need is automated "acceptance" testing where I simulate user interactions on the "full stack". So I was looking into launching the full Neutronium app with
npm run dev
serving up the JS. I was able to get it to work by replacing the following options in webpack.config.js:and replacing the Uri in MainWindow.xaml:
The only problem is that when JavaScript code is updated, the browser window contents are reloaded, and I get an error that Vue is not defined...
Two Questions/Requests:
What do you think of this approach? I think it would be a better debugging and testing experience since you wouldn't have to wait for
npm run build
to run a Neutronium App in debug mode, and we could use test runners like Karma to launch our "custom" (Neutronium) browser window and do fully automated acceptance testing.... I'm also open to alternatives you may have tried.
Best,
Michael
The text was updated successfully, but these errors were encountered: