by Richard | Nov 29, 2017 | Culture, Testing
When teams start out with writing tests for their codebase, it’s very common to have difficulties because certain types of code are harder to test or “untestable”. A mistake that’s commonly made is to try to use mocks or similar, and make a...
by Richard | May 9, 2017 | Testing
Having good test coverage is invaluable to a software team, because it gives them the ability to make changes and quickly see the results. A good test suite serves 2 main purposes: it provides a safety net that shows the impact (intended or otherwise) of changes to...
by Richard | Feb 1, 2017 | Testing
In order to deliver software, the team need to have confidence in its quality and robustness. The category of activities used to establish that confidence is broadly known as “testing”, but within this overall label there are many different forms of...
by Richard | Jan 24, 2017 | Testing
The first service oriented system I worked on was for a retailer, processing the lifecycle of customers’ orders from purchase through dispatch and a customer service cycle. At launch, the system had performance issues which my team was tasked with identifying...
