Are...are you trolling? Because I am flabbergasted.
I mean, it's one thing to have a healthy discussion around how much testing should be done, or what type of tests should be written, or what parts of an app should be tested. But you are suggesting zero tests. If you are building a prototype for validation, sure that's fine because it's not a real app and people using it know that its not real. But as I read this you are suggesting that people should deploy a production system for real people to use without any tests, YOLO style, because you need their feedback before you can solidify your design. And that is bonkers to me.
I hope to the FSM that your app doesn't do any sort of e-commerce, or authentication, or take user input of any kind.
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/
Are...are you trolling? Because I am flabbergasted.
I mean, it's one thing to have a healthy discussion around how much testing should be done, or what type of tests should be written, or what parts of an app should be tested. But you are suggesting zero tests. If you are building a prototype for validation, sure that's fine because it's not a real app and people using it know that its not real. But as I read this you are suggesting that people should deploy a production system for real people to use without any tests, YOLO style, because you need their feedback before you can solidify your design. And that is bonkers to me.
I hope to the FSM that your app doesn't do any sort of e-commerce, or authentication, or take user input of any kind.
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.