[RFC] Add test runners to project during quasar init about quasar-starter-kit

[Arushi-Jain]

Thank you for your insights, I will definitely look into it.

[Arushi-Jain]

In order to download testing dependencies along with the quasar template, I forked the quasar-starter-kit and changed the package.json. It downloads only the dependencies for unit test for now only when the user says yes to the question asked (edit meta.js to change the questions asked).
Quasar-cli is needed only to create the folder for those tests, for now I create the folder myself for unit testing while the dependencies are downloaded only i choose to.

[nothingismagick]

Regarding your comment in general, we have moved to babel7 and webpack4 - your package.json shows that your source is not up to date with quasar 0.16.1...

[Arushi-Jain]

But this approach will even work, we are just creating our own template using quasar-starter-kit .
with quasar 0.16.1 we may have to change the version of the webpack loaders in webpack.test.config.js

[nothingismagick]

Yes, your approach would theoretically work, but the thing is that we want to centrally manage the packages installed for the various test runners. We are not merely offering mocha-webpack. Further, this approach does not hook into the webpack chain of quasar 16+ - which in my opinion is the only reason to use mocha webpack. Otherwise just use jest or Ava...

[nothingismagick]

For your information, I was also able to integrate mocha-webpack into quasar 15, it is Babel and the new webpack approach that makes it challenging with 16.

[alansoliditydev]

why use mocha instead of jest?

Jest is very strong supported by facebook, we will need jest snapshot & image snapshot to get pixel perfect test for UI.