Remove Blog Remove Software Review Remove TDD Remove Testing
article thumbnail

TDD mistakes 2

Habitable Code

Back in 2014 I wrote a blog post listing three mistakes often made by folks who are new to test-driven development (TDD). Writing tests for invented requirements. Writing a dozen or more lines of code to get to GREEN. How shall we test it?”

article thumbnail

TDD: Three easy mistakes

Habitable Code

Back in 2014 I wrote a blog post listing three mistakes often made by folks who are new to test-driven development (TDD). Each time I visit a team that is relatively new to TDD I find the same basic mistakes cropping up every time. Writing tests for invented requirements. This is part 1.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

TDD mistakes 3

Habitable Code

Back in 2014 I wrote a blog post listing three mistakes often made by folks who are new to test-driven development (TDD). Writing tests for invented requirements. Writing a dozen or more lines of code to get to GREEN. It is also not TDD. So, what did you find when you tried to get the test above to GREEN?

article thumbnail

Xebians collaborating on internal tool development

Xebia

However, the purpose of this blog is not just to describe the toolset, but to share our development approach and some valuable lessons I (re)learned along the way. Without a clear design, we use pair programming and test-driven development (TDD) until we are satisfied, focusing on the desired API first.

article thumbnail

TDD + data driven with Jest

StubHub

During my years as developer, I have faced several troubles in production due to bugs. For me, this is a huge problem because I love to sleep, and I cannot sleep well if I have doubts about the quality of my code. Because of this, I started some years ago to study how to sleep well, which came down to learning about testing my code.

article thumbnail

Don't Measure Unit Test Code Coverage

James Shore

James Shore/Blog. If you're using test-driven development, don't measure unit test code coverage. To improve code and test practices. If waiting for defects to escape is too risky for you, have experienced QA testers conduct exploratory testing and conduct root-cause analysis on the results.

article thumbnail

Using Golang for your Serverless projects

Xebia

In one of my previous blogs I wrote why I switched to compiled languages for my lambda functions. In this blog I would like to share the challenges that I have seen and how to mitigate them. Spoiler, I use a Makefile I always use a Makefile in my projects, If you are interested in why I wrote a blog on that as well.