ytest is a PHPUnit extension, based on the PHP extension "runkit", that allows you to replace static, private, and global functions with fakes, stubs, or mocks. This eases the automated testing of PHP applications that weren't written in a TDD fashion (i.e. test-first). It can also be helpful on projects where many methods are kept private, or projects that don't use OOP so much. ytest has already been used to "test after" (as opposed to "test first") some real-life commercial projects, and has proven useful. It needs PHP >= 5.2.
SOAP/REST Mock Service is a simple configurable framework to mock out SOAP or RESTful (or "REST-like") Web services. Its main goal is to support automated integration testing of applications that integrate with 3rd party Web services. Functionality and usage scenarios of the mock service are in a way analogous to unit testing mocking tools (like Mockito or EasyMock). Once properly configured, SOAP/REST Mock Service exposes Web service mocks that can be called from application code and controlled via a REST interface from integration test code (setup, verify, etc.).
cmocka is a unit testing framework for C with mock objects. There are a variety of C unit testing frameworks available supporting different platforms and compilers. Some development requires a lot of different compilers and older versions, which makes it difficult to use unit testing frameworks. The idea of CMocka is that a test application only requires the standard C library and CMocka itself to minimize the conflicts with standard C library headers, especially on a lot of different platforms.
CaptureMock provides capture-replay mocking for Python, on the command line and with client-server communication. CaptureMock's approach is a so-called capture-replay approach. This means that when you 'record' your mock, CaptureMock will observe the interaction between your code and the subsystem you are mocking out, and record it in a text file in its own format. When you then run your test in 'replay mode', CaptureMock can play the role of the subsystem in question, and the real subsystem does not need to even be installed. You can then choose, each time you run your tests, whether you wish to have the real subsystems present and verify/recreate the captured mocks, or to rely on the mocks captured by a previous run. If you are running in 'replay mode' and CaptureMock does not receive the same calls as previously, it will fail the test, and suggest that you may want to recreate the mocks in record mode.
Flexmock is a mock/stub/spy library for Python. Its API is inspired by a Ruby library of the same name. However, it is not a goal of Python Flexmock to be a clone of the Ruby version. Instead, the focus is on providing full support for testing Python programs and making the creation of fake objects as unobtrusive as possible. Flexmock’s design focuses on simplicity and intuitiveness. This means that the API is as lean as possible, though a few convenient short-hand methods are provided to aid brevity and readability. Flexmock declarations are structured to read more like English sentences than API calls, and it is possible to chain them together in any order to achieve high degree of expressiveness in a single line of code.