5 ms·
This is one of the problems that TDD tries to solve. To make changes to a small piece of code, you don't want to have to go through a huge iteration of running
by weavie 13y ago
This is one of the problems that TDD tries to solve.
To make changes to a small piece of code, you don't want to have to go through a huge iteration of running up your server, going to your browser, moving around the app to get into the required state and then trying out the bit of functionality. No, you just write a test for that bit of code and run it. No browser needed.
The cycle he describes is what you do at the very end. Once.
- ereckers 13y agoI thought the problem he was trying to solve was to speed up simple things like text color changes or pushing elements around a few pixels. TDD doesn't try and solve that does it?
- coob 13y agoIf anything it makes more of a PITA
- tuxcanfly 13y agoFrom my experience, frontend tests break easily in unexpected ways e.g. div moved by an inch? Error - element-not-visible!
- jasonkarns 13y agoDepends on your definition of frontend tests. TDD alleviates these workflow problems for javascript (the actual code of the application). But using automated tests for the UI layout is gonna be a bad time. As @davemo mentioned, this post seems primarily directed at a designer's workflow with CSS and less about javascript development.
- weavie 13y agoAh yes true. I glossed over the CSS bit and just took in the javascript bit. I don't think TDD would fix a CSS workflow.