GitHub "damphyr/bare_unity" - “The C code is untouched. What has changed is the way the test runners are generated. To that purpose the original scripts are all gone and in their place there is a single generator that uses an ERB template to create the test runner. In the original Unity test runner generator the runner's C code is embedded in the Ruby script. This makes it difficult to adapt the runner with C code to i.e. run in a specific embedded device”.

Working principle: The source code of this testing application has to be included in the project sources.

The OpenSource SourceForge "CMock", SourceForge "CMock" - “A module/object mocking framework for C projects. It generates dummy modules that conform to the interface specified in a header file. This allows APIs to be proven out and exercised before committing to an underlying implementation”.

Microsoft MSDN - The Visual Studio Blog "Visual Studio Express 2012 for Windows Desktop", 2012-06-08 - “With this new Express edition, developers will be able to use C++, C#, or Visual Basic to create Windows desktop and console applications. Developers will also get access to new advances available across the Express family in Visual Studio 2012, such as the latest compilers and programming language tools, integrated unit testing, and the ability for small development teams to collaborate via Team Explorer and TFS Express”.

A solution may contain several projects. A project may hold everything needed to generate an executable application. Unit test for testing the code of a project are kept in extra test projects. So with “File / Add / New Project / Visual C# / Test”, you may add a test project.

Set the Testrunner as startup project ( Mouseclick-right on the project in the “Solution Explorer” window, select the menu item “Set as Startup Project” ).

The project to be debugged may be either of the type “Windows Application” ( .exe ) or “Class Library” ( .dll ), in the project properties at “Application / Output type”.

In the project properties, set “Debug / Start Options - Command line arguments” to ”..\..\..\FizzBuzz\bin\Debug\FizzBuzz.exe” or ”..\..\..\FizzBuzz\bin\Debug\FizzBuzz.dll” respectively, so that the TestRunner calls the project to be tested, properly.

In 2015-12 expert considered it to be the “ultimative successor of Mocha” .

“Futuristic test runner”.

“Even though JavaScript is single-threaded, IO in Node.js can happen in parallel due to its async nature. AVA takes advantage of this and runs your tests concurrently, which is especially beneficial for IO heavy tests. In addition, test files are run in parallel as separate processes, giving you even better performance and an isolated environment for each test file... Having tests run concurrently forces you to write atomic tests, meaning tests don't depend on global state or the state of other tests”.com/forum/#!topic/nodejs/V16D4D4FUWU|Google Groups “nodejs”, Thread “describe is not defined”]] - “My understanding is that to run the tests with mocha, you must run 'mocha', because mocha creates the 'describe' function, among others. You cannot run the tests by running 'node'”.

With PHPUnit 5.5.2, the class “TestCase” is implemented. The online documentation is just for software versions with implemented class “TestCase”.

With XAMPP, PHPUnit is shipped as file “phpunit” without file extension, e.g “C:\xampp/php/phpunit”. When updating the installation by a PHAR archive, the updated file must be renamed so that there is no file extension ( e.g. “ren phpunit-5.5.2.phar phpunit” ).

Python Package Index "hypothesis", GitHub "DRMacIver/hypothesis" - “Hypothesis is a library for testing your Python code against a much larger range of examples than you would ever want to write by hand. It’s based on the Haskell library, Quickcheck, and is designed to integrate seamlessly into your existing Python unit testing work flow”.

Windmill Testing Framework - “Windmill is a web testing tool designed to let you painlessly automate and debug your web application”, “Interact with the browser and the windmill service from a python shell”.

Github "idealistdev / alfajor" - “Tasty functional testing”. “Alfajor provides a modern, object-oriented and browser-neutral interface to HTTP resources. With Alfajor, your Python scripts and test code have a live, synchronized mirror of the browser's X/HTMLDOM, even with DOM changes made on the client by JavaScript.”.

The OpenSource SourceForge "CMock", SourceForge "CMock" - “A module/object mocking framework for C projects. It generates dummy modules that conform to the interface specified in a header file. This allows APIs to be proven out and exercised before committing to an underlying implementation”.

Books written and released before 2006 do not cover JUnit 4, but just JUnit 3. Take care of new editions of old books, and of german translations of english books originally written and released before 2006, which still just deal with JUnit 3 !