Technical debt. Bringing features live faster by taking shortcuts in the source-code. As a result, future features are harder to build because the source-code got more complex.
The same applies to testing. A lack of automated tests slows a team down and makes it more complicated to release software. Especially, when you’re just getting started with continuous delivery, there is few test-automation, if any at all. Fixing it all in one go is too much work. So, how do you deal with that? Read More
The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created.
So why not release every sprint?
Releasing more often is easier said than done. The release frequency of a product depends on the time it takes to test it. Changing a line of code is easy. Testing that change is a lot more difficult. And it’s usually a bad idea to release untested software.
Implementing test automation in an existing codebase can take serious effort. It does not only change the code, but it also changes the way of working. So where to get started?
A unit test is a small automated check. It checks a tiny bit of software. Unit tests can be written relatively… Read More
DevOps teams automate everything. When you’re getting started with test automation, it’s important to wonder why someone would want to automate tests. And what is testing, anyway? This article describes what testing is and what parts of that process can be automated. Fortunately, there’s no way test automation will eliminate manual testing; it will just make that process more efficient. Read More