article thumbnail

Agile Book Club: Test-Driven Development (with Mike “GeePaw” Hill and J.B. Rainsberger)

James Shore

Test-Driven Development is one of the few truly new Agile ideas. Originally created by Kent Beck as part of Extreme Programming, it’s a fantastic way of making sure your code does what you intended it to do. It’s not perfect, but it’s a powerful tool for creating robust and reliable software. Rainsberger.

article thumbnail

Code analysis tool AppMap wants to become Google Maps for developers

TechCrunch

The 10/10-rated Log4Shell flaw in Log4j, an open source logging software that’s found practically everywhere, from online games to enterprise software and cloud data centers, claimed numerous victims from Adobe and Cloudflare to Twitter and Minecraft due to its ubiquitous presence. Image Credits: AppMap.

Insiders

Sign Up for our Newsletter

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

article thumbnail

AoAD2 Practice: Test-Driven Development

James Shore

To share your thoughts, join the AoAD2 open review mailing list. Test-Driven Development. We produce high-quality code in small, verifiable steps. At best, mistakes lead to code that won’t compile. No wonder, then, that software is buggy. There is such a tool, or rather, a technique.

article thumbnail

Test Driven Development with Databricks

Perficient

I don’t like testing Databricks notebooks and that’s a problem. I like Test Driven Development. Not in an evangelical; 100% code coverage or fail kind of way. I just find that a reasonable amount of code coverage gives me a reasonable amount of confidence. I like Databricks. They are very good.

article thumbnail

Agile, Stand-ups, TDD and Code Reviews

The Programmer's Paradox

It all has to be very reactive; you keep fiddling with the code until it gets traction. Under those conditions, it doesn’t make sense to cross all the t’s and dot the i’s as the life expectancy of the code is weeks or months. We see the same kinda thing with unit testing. So you build, pivot, build, pivot, etc.

article thumbnail

Test Driven Development with Databricks (1 of 2)

Perficient

I don’t like testing Databricks notebooks and that’s a problem. I like Test Driven Development. Not in an evangelical; 100% code coverage or fail kind of way. I just find that a reasonable amount of code coverage gives me a reasonable amount of confidence. I like Databricks. They are very good.

article thumbnail

5 ways to do Continuously Improved Testing

Xebia

It is okay to start out simple and not overthink, but these two things are key: Have tests – having some tests is better than no tests, as it provides a feedback mechanism for improvement. This results in a steadily-growing set of tests becoming part of the development cycle. Independent. Repeatable.

Testing 130