Why People (Don't) Write Automated Tests?

49.4% of the respondents don't have time to write tests. Why? Let's discuss.

My other videos:

- - - - -

[mwuftfw]

Thank you. I spend couple hours to figure out test fundamentals in Laravel — made some tests to check routes to get normal server response and some user permission checks. In first time it took some time, but next time it will be much quicker.. And so now i don't afraid to "spend lot of time for test".. But if i would think "100% coverage or nothing" i would chouse "nothing".

[invigale]

that's why QA profession exist. I don't even have time to refactor my code because I already have tons of existing tasks that are really needed weekly. refactoring without enough time or doing new features at the same time introduces problems more than solution.

[Co-Monad]

Writing tests is just like any other skill. The more you do it the better and faster you are at at it. You’re probably not writing tests if you’re early in your career, freelance or not, working alone, or maybe there’s a dedicated SDET.QA. Having done freelance and worked at large companies I’ve gotten to a point we’re I use the test diamond paradigm and have automated 90-95% of the frontend which covers visual regressions, various states, and I integration. I even have a repo for e2e that leveraged functional programming puppeteer and/or cypress and cucumber.js. A few lines of gherkin syntax from anyone, even non technical people if needed and presto. It takes very little time now days to ensure a project has a high degree of confidence and stability. I prefer releases being non eventful. All tests are not created equal. Choose wisely based on your risk tolerance and team size.

[pitisradu]

Always curious about how to "budget" a project.
It would be a nice addition to talk about budgeting for apps, since if you tell clients about testing the most obvious response they'll have is "No, I want it faster and without more money". How do we just tell the client in a way in which he'll agree: "hey, this is a better way to check for errors but it takes more to deliver? and ofc you also have to pay"?

[leonardBeni]

For me, who works for software developer agency.. when i want write test, it was only anoy my PM.. even i wan't to... For my personal projects, i always write rigorous test unit...

[QiYang]

Tests are also code that would introduce bugs, and every future change would also require changing your tests first. For small projects this just seems not worth it when the developers are focusing on the product itself. For large projects, the benefit is much bigger, however the tests are usually written by QA/QC people.

[SebastianPerezG]

Test only is useful if you have a LONG TERM development, for me, with one o two week projects, i don't need it.

[simplydeveloper]

Nice... I am also creating some laravel video...

[SilverWave]

If you’re under pressure and have to keep deadlines, it’s really hard because tests are extremely time-consuming. Thinking of every single scenario is hard. You’re testing the application yourself afterwards anyway. Also, some tests will change entries in the database, which is risky. And if you change a feature afterwards, you need to change all of the tests too. Is so unbelievably annoying.
Overall, it’s unnecessary, extremely time-consuming and just not worth it.