A year ago I was tasked to test typical Microservices-based project with modern frontend and the tra...
A year ago I was tasked to test typical Microservices-based project with modern frontend and the traditional tools just didn't work for me. So I went into a journey of finding modern techniques that might score better and guess what: I discovered a handful of neat techniques that rocked my testing world. Let's discuss when the traditional testing tools fall short and how modern and emerging techniques can sometimes do better: In the past 10 years, the dev world had gone through dramatic changes but the testing models were left intact leaving us wondering how to test things like Microservice, and Serverless. This session demonstrates the new wave of testing tools (e.g. property-based testing, consumer-driven contract, fuzz, and others) and how they can better fit modern applications. This session aims to inspire with modern testing ideas, but it also packs practical and down-to-earth code demos. About me - Yoni Goldberg: I'm an independent consultant who works with 500 fortune corporates and garage startups on polishing their JS & Node.js applications. I'm also the author of Node's largest best practices collection: https://github.com/i0natan/nodebestpractices
This is a story of how we were able to go from zero automated testing, static analysis, end to end t...
This is a story of how we were able to go from zero automated testing, static analysis, end to end testing, and a lot of wasted time, broken deploys and pager duty requests to being able to deploy changes on a Friday at 5pm. I did this by slowly getting buy in from team members over the course of the first year I was working at System1 and introducing checks and tests slowly, instead of doing what many well meaning engineers do of trying to introduce too much all at once. Turning on tests 100% in a blank document is easy, integrating it into a 4+ year code base is not. I'll cover: 1. The point of testing (it's actually to speed up releases, not necessarily catching bugs!) 2. The low hanging fruit big wins you can make at work tomorrow (it's not trying to convince business to give you 4 weeks to write write brittle end to end tests and not push out features). 3. The tricks to introduce eslint, Typescript, Jest, and Mabl/Cypress slowly without annoying other engineers to the point of them just turning it off. 4. The before and after results of how testing has speed up System1's frontend team to release 2-3 times a day without breaking a sweat instead of a once a week ordeal.
Our next location
after the talks, around 9:15