I'd like to make slack more vivid by sharing experiences about our projects with chimp as the evolution of chimp is upcoming.
Are there further resources or discussion boards?
I'm currently writing a blog collecting knowledge about specs and automated testing. I'm glad for any input (and like to relate to your pages).
I'm working with cucumber.js and I'm sure the newest version will be implemented. I also use Meteor. My focus is to push testing in js forward.
I am happy, that there is chimp, which makes it easier to start. Of course, there is cypress.io and else. Yet, I wanna see chimp leverage.
I also wish to learn more skills by extern training. I think I will call the brain family in future.
I appreciate your opinions to my mentioned topics. Thx =D
[Łukasz Gandecki, Xolv.io Community] We differ with Sam here a bit. I recommend Cypress :) Much better dev experience. It is coupled with a bunch of tools (like mocha), and it’s own API, but to be honest webdriverio is not so different, you will probably use it with their own runner, which means any testframework you use you will also have to use their wrappers (cucumber-framework, mocha-framework, etc). So it’s not very different from cypress I’d argue, with that difference that they give you more choices. From a practical standpoint it doesn’t really matter that much if you use Cypress with mocha or jest for example, since the testing syntax is virtually the same, and the assertions are done through cypress API anyway.
I’d probably recommend building a small test suite with both and seeing what feels better.
[Sam Hatoum, Xolv.io Community] One day @lgandecki and I will agree. For now, you can have fun watching us argue :)
I think if you're wanting to test a whole app, that is: your testing strategy revolves around end to end testing, then Cypress gives you great tooling for creating scenarios after the fact. It's a great replacement for record/playback tooling. It's great at waiting for DOM events etc.
If your testing strategy revolves around testing domain driven design and/or decoupled architecture, and you want to do example guided design (aka TDD/BDD), where you 1. specify an example 2. automate it and 3. implement it, then I see more modular testing tools as the better solution since each boundary will require different tooling, and no one tool can be there best at everything.
For UI based example guided design, I prefer to test isolated modules at a unit level, and have contract tests for integration. So I'm my testing strategies, I have only a handful of end to end tests, and for those I like to drive then with tests which means the events will be predictable and I don't need tooling to wait for DOM events. I can design a predictable system instead.
Cypress is a testing monolith that has a large footprint and a long startup time. Yes you can optimize it, but why bother when you can be modular?
npm ERR! code ENOLOCAL npm ERR! Could not install from "node_modules/chimp/glob@github:lucetius/node-glob#51c7ca6e69bfbd17db5f1ea710e3f2a7a457d9ce" as it does not contain a package.json file.