TestLess 1.8.2, containing a bug fix and a few other minor improvements, has been released! You can purchase TestLess, or download a trial version now!
In this post, I’ll illustrate the workflow that you can use to extend TestLess so it can analyze any test suite. I will use a real example from a real customer to show you how easy it is to extend TestLess. The Problem Recently, I received the following question from a customer: I’d […]
Out of the questions that customers ask about TestLess, the one that crops out the most is: how can I create my own TestDetector for my language and/or test-style of choice? In other words: how do TestDetectors work? I’ll clarify and answer those two questions in this post. TestLess comes equipped with several TestDetectors out of […]
In this post we take a quick look back at the success stories for Mutator and TestLess that you might not know about: Bloom Filters Bloom filters are everywhere nowadays, and having seen the quality improvements that Mutator started, it is no wonder that the authors of one popular implementation decided to continue on that road. Best of Breed Mutator […]
BDD-style testers: Rejoice! One of the super helpful aspects of BDD test frameworks is their utilization of nested contexts. Nested contexts not only allow test writers to group different tests, but also allow you to delineate their state into different sets in order to separate permutations of their SUT’s (system under test) behavior into logical groups. This separation and […]
You asked, we listened! We heard you loud and clear and we are thrilled to introduce multi-source support for Mutator! Previously, Mutator only allowed one source file per test suite using the assumption that each test suite had one and only one source (a.k.a. system under test, or SUT). This original design choice was deliberately made partly to encourage […]
Case Study 3: Find repeated test names JRuby is a high-performance, fully-threaded Java implementation of the Ruby programming language. To test and stabilize JRuby, the core team employs several distinct test suites from different sources such as MRI tests, the JRuby team’s own internal tests, rubspec, rubicon, and others. This means that there are probably between 1 to 1.5 […]