René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Is it possible to make this driver support Jest for NativeScript-Vue users?","articleBody":"**Is your feature request related to a problem? Please describe.**\r\n\u003c!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]. --\u003e \r\nWhile I am aware that Mocha, Qunit, and Jasmine are what is described to be the recommended test runners in NativeScript-Angular. With NativeScript-Vue, it appears that the community has not fully agreed on a [proper test setup](https://github.com/nativescript-vue/nativescript-vue/issues/224)  or runner. So far the NativeScript-Vue community  have agreed to make Jest the [standard test runner](https://github.com/nativescript-vue/nativescript-vue/pull/486) for unit and integration testing so utilities such as Vue Test Utils can be used. However, it appears that it is still not possible to run Jest reliably with nativescript-dev-appium as it crashes with a [reserved name error](https://github.com/appium/appium/issues/10237)  in the dependency [cloudhead/vargs](https://github.com/cloudhead/vargs) which has not been maintained for 10 years. Having to use another test runner for e2e and Jest for everything else is a problem as it is not best practice to mix test runners.\r\n**Describe the solution you'd like**\r\n\u003c!-- A clear and concise description of what you want to happen. --\u003e\r\nI know similar write once mobile frameworks such as React Native are able to use Jest as an Appium test runner through a [babel preset](https://medium.com/front-end-weekly/how-to-do-end-to-end-e2e-testing-for-react-native-android-using-jest-and-appium-27d75e4d831b) and just using the standard wd driver. So I was wondering if it would be possible to make this driver work for Jest so the NativeScript-Vue users can use the same test runner throughout all stages of testing. Whether it would be possible through a new babel preset or replacing cloudhead/vargs with the new [mike-lang fork](https://github.com/mike-lang/vargs/commits/master) of vargs, or even just creating a separate driver or driver-extension for NativeScript-Vue. Otherwise if changes need to be made to other dependencies, perform a pull request. If it is not possible to create such a feature feel free to inform about the limitations and what alternatives to consider.\r\n\r\n**Describe alternatives you've considered**\r\n\u003c!-- A clear and concise description of any alternative solutions or features you've considered. --\u003e\r\n\r\nAlternatives considered have been to run [Vue Test Utils with mocha-webpack](https://vue-test-utils.vuejs.org/guides/testing-single-file-components-with-mocha-webpack.html)  which has been unsuccessful in a NativeScript environment, just do [manual Vue component testing](https://vuejs.org/v2/guide/unit-testing.html) with other runners which can make tests more tedious in the long run, or just run Jest and other test runners in tandem and block jest from any e2e directories which is quite ugly. \r\n\r\n**Additional context**\r\n\u003c!-- Add any other context or screenshots about the feature request here. --\u003e\r\n","author":{"url":"https://github.com/redelman431","@type":"Person","name":"redelman431"},"datePublished":"2020-02-04T17:58:32.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/283/nativescript-dev-appium/issues/283"}