We all want “better” test suites. But what makes for a good test suite? Certainly, test suites ought to aim for good coverage, at least at the statement coverage level. To be useful, test suites should run quickly enough to provide timely feedback.
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.
This presentation gives you a few code review tips for keeping your code healthy and your team happy. You will learn why talking about code in person is important, how to talk about code without burning bridges and, most importantly, how to take dread out of your workplace.
Tomek Kaczanowski writes that the idea behind its “Bad Tests, Good Tests” book is “to present test code snippets and discuss ways of making them better.” To achieve this goal, he explores a large amount of code and tests to discuss all the issues that you can meet in your software testing activities.
Personas are fictional archetypes based on the real world that represent a group of users who have common goals. This is a concept that is often used in product and software development. In this blog post, Katrina Clokie expand the concept of personas to the software testing domain.
Concurrency has become an increasingly important topic in the Java space. Nevertheless, most Java developers do not address concurrency in their unit tests. This talk shows how to and how not to test concurrent code and introduces Thread Weaver, a library for testing concurrent code.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates