I don't think Kevin's suggesting zero tests, but rather meant it as avoid pre-maturely writing tests.
Like when you haven't figured out if people want what you are building, don't write those tests yet. I would even say, don't even build stuff before you validated that people want it - you can survey or show people mockups to validate demand first.
Like when you haven't gotten a firm grasps of your front-end stack, don't write those tests yet, because unit-tests like Jest can requires a fair bit of planning beforehand.
And like and when you've got tests that aren't connected to your pipeline, don't write more tests yet. Connect those existing ones first, before moving on the writing new tests.
Front-end Engineer and Tester. I have a course at https://learn.webdriver.io and I do free coding tutorials at https://www.youtube.com/user/medigerati/
I don't think Kevin's suggesting zero tests, but rather meant it as avoid pre-maturely writing tests.
Like when you haven't figured out if people want what you are building, don't write those tests yet. I would even say, don't even build stuff before you validated that people want it - you can survey or show people mockups to validate demand first.
Like when you haven't gotten a firm grasps of your front-end stack, don't write those tests yet, because unit-tests like Jest can requires a fair bit of planning beforehand.
And like and when you've got tests that aren't connected to your pipeline, don't write more tests yet. Connect those existing ones first, before moving on the writing new tests.
Yes, this exactly!
Sorry I wasn't clearer in the post. Sometimes I end up having a lot written in my head that I forget to put down in the text.