Another attempt to help devs embrace writing tests. Did you ever felt a huge discomfort every time you have to write a test (case) for a quite big (with complex logic) vue component? I have everytime I come across one specific container. Having huge containers is quite bad. And it…

Part II — non developer way. First part can be found here: Adding “Human” touch to testing (vue) app. Part I — developer way.medium.com In the part I we “quickly” added cypress to our vue app. With the help of plugins we added some magic to our app. …

Part I — developer way. EDIT: Part II is out: Adding “Human” touch to testing (vue) app — II. Part II — non developer way.medium.com And by “Human” I mean adding a tool that will simulate the user. Yep, it’s about tool/library that will help to test app from user’s perspective. Let’s find a “victim” first — one vue app that without e2e integrations. And…

This might fix some fears. Sometimes we end up with some logic if/elseif/else in our vue hierarchy. This might be because of complex logic or pure architectural skills. In my case, I had the “pleasure” of both. I had a container that have to display data (from store) in create…

Edit 6/11/2019: added vscode extension: ext install vitalieandries.vscode-vue-lazy-snippets First step is always hard. However, if there is a chance to become a better developer, why not to take it?! Here I’ll be focusing on hard side: vue class component+ typescript + jest. …