Tutorials and resources on how to apply unit testing in software testing
As distributed systems are too complex for deterministic testing, AI can help. In this article, Naveen Prakash proposes an approach based on the ideas of chaos engineering and AI-assisted testing. The focus shifts from testing individual pieces to understanding what happens when many services run together under unpredictable conditions.
This talk aims to introduce property-based testing, why you may want to use it, and real-life use cases for including it in code bases. Property-based testing is an approach to testing that involves specifying statements that should always be true (for example, reversing a list twice will give the original result) rather than relying on specific examples.
Database testing is one of the areas that might have the smaller number of open source tools. The programming languages have many xUnit tools and mocking frameworks, but this is not the case for databases. This article provides a list of open source tools that can be used to perform unit, load and security testing on several relational (MySQL, Oracle, SQLServer, etc.) and NoSQL databases.
As unit testing is often the first quality activity targeting code during the software development lifecycle, this article considers several examples of effective approaches to the naming of unit tests.
This presentation shows how you can take advantage of the most recent additional to the unit testing tools in Visual Studio to build more reliable apps. Besides Visual Studio own tools, you can also run unit tests in Visual Studio by using third-party test frameworks such as NUnit, Boost, or Google C++ Testing Framework, depending on your programming language.
“TDD is a design tool.” That is what the presenter has said for years. But not anymore. After working with different teams and in different organizations, and also carefully inspecting how he works, he changed his mind about the role of Test-Driven Development (TDD) in software design.
The paradox: I cannot test this code because it is legacy. I need to refractor the code to make it testable. How can I manage that, without breaking existing functionality? I will need to write some tests, but… argh! This presentation explains how to safely refactor and test ‘untestable’ code – without breaking any existing functionality.
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates