Tutorials and resources on how to apply unit testing in software testing
Unit Testing has moved from fringe to mainstream, which is great. Unfortunately, developers are creating mountains of unmaintainable tests as a side effect. Jay Fields has been fighting the maintenance battle pretty aggressively for years, and this talk captures what he believes is the most effective way to test.
Mockito is a popular open source mocking framework for Java code. In this article, Marcin Grzejszczak explains how you can use Mockito by adding it to different paths. You will also learn how to implement new tests by using Mockito hints and warnings.
One of the famous concept in software testing is the testing pyramid defined by Martin Fowler that is based on strong unit tests and has less user interface (UI) tests at the top. Sometimes organizations have a different view of software tests and the pyramid is not a pyramid anymore. In this blog post, Fabio Pereira discusses the case where the pyramid looks like a cupcake.
Writing test should be part of the normal routine of every software developer. It is however not always the case. In his book ” Bad Tests, Good Tests”, Tomek Kaczanowski provides some interesting tips to improve your test writing activity.
There is always a lot of discussions about the costs and benefits of unit testing. The opposition was exacerbated by the adoption of Test-Driven Development (TDD), a technique that recommends writing unit tests before you write the code. In this blog post, Steven Sanderson discusses unit testing with a costs and benefits perspective.
This talk shares some experience with JavaScript tests, and show the most important patterns you can rely on to write simple, beautiful, maintainable and incredibly fast tests.
Unit testing is always causing some debate about its usefulness in the software development community. Some developers argue that unit tests are a waste of time because they provide few value to assess the quality of the final system and they are difficult to maintain. In his Henrik Warne explains why he thinks that you get a lot of value from unit tests.