Search Results for "all to"

NUnit is a unit-testing framework for all .Net languages. Initially ported from JUnit, the current production release, version 3, has been completely rewritten with many new features and support for a wide range of .NET platforms. NUnit is intended to be extensible. We can't do everything for everybody but we want to make it reasonably easy to extend NUnit. In many cases, users will be able to implement a special feature outside of our scope by simply creating a new attribute that embeds the required logic. ...

...Fake timers are synchronous implementations of setTimeout and friends that Sinon.JS can overwrite the global functions with to allow you to more easily test code using them. A test spy is a function that records arguments, return value, the value of this and exception thrown (if any) for all its calls. There are two types of spies: Some are anonymous functions, while others wrap methods that already exist in the system under test. Mocks should only be used for the method under test.

The VBScript Development Kit (VDK) is a VBScript compliant development library to be used in any host that has support for Windows Script Host (WSH). Modelled after the Java Development Kit (JDK), the VDK adds programming features/concepts prevalent in other higher order programming languages such as Java, C#, etc. The VDK provides rapid development capabilities by providing out of the box support for many common programming activities e.g., string manipulation and handling, file...

FORTRAN Unit Test Framework, written in FORTRAN 95. So that all FORTRAN features can be tested. FRUIT has assertion, fixture, setup, teardown, report, spec, driver generation. Rake used as build tool. Tutorials at http://fortranxunit.wiki.sourceforge.net The core testing part is in FORTRAN, this part can be used independent of the Ruby codes. The Ruby code is to make fixtures and reports easier.

We are moving: Download the newest version directly at https://tSQLt.org -------------------------------------------------------------------------- tSQLt is a unit testing framework for Microsoft SQL Server. tSQLt is compatible with SQL Server 2005 (service pack 2 required) and above on all editions. tSQLt allows you to implement unit tests in T-SQL. This is important as you do not have to switch between various tools to create your code and your unit tests. tSQLt also provides the following features to make it easier to create and manage unit tests: * Tests are automatically run within transactions – this keeps tests independent and reduces any cleanup work you need * Tests can be grouped together within a schema – allowing you to organize your tests and use common setup methods * Output can be generated in plain text or XML – making it easier to integrate with a continuous integration tool

NUnit brings xUnit-style unit-testing to all .Net languages. Although we no longer host our development on Sourceforge, our latest releases are always available here, as well as at our current development site at http://launchpad.net/nunitv2 Please report bugs at http://bugs.launchpad.net/nunitv2 You can browse or download the current source code at http://code.launchpad.net/nunitv2

The project moved to GitHub, https://github.com/aevdokimenko/tsqlunit TSQLUnit is a framework to write tests for applications written in Transact-SQL. It follows the tradition of the "xUnit" framework that is available for almost all programming languages.

PublicTest is an automated unit testing tool. In essence, it changes all private/protected accessibility members to public, allowing direct testing of members that would normally be inaccessible to a testing class.

Testsweet is a unit testing tool to ensure that all tests in a project are being run, by either auto generating unit test suites at runtime, or ensuring that all tests in a project are included in a static suite at build time.

Embedded Unit is unit testing framework for Embedded C System. Its design was copied from JUnit and CUnit and more, and then adapted somewhat for Embedded C System. Embedded Unit does not require std C libs. All objects are allocated to const area.

An unit testing framework (http://www.xprogramming.com/software.htm) to allow unit testing of Products in a real Zope environment, with all the bells and whistles.