Search Results for "documentation"

PyKCS11: a complete PKCS#11 wrapper for Python, created using the SWIG compiler. API documentation: http://pkcs11wrap.sourceforge.net/api/

QTest is a perl-based test framework for testing programs written in any language. It supports a "design for testability" mentality, user-defined test coverage, filters, and multithreading support. Includes documentation.

simple-test was developed to make C++ code testing easy. A test can be implemented using just one single header file.

...Go to https://sourceforge.net/p/mockerplusplus/code/ci/master/tree/ Download everything except copy-tools.sh (which is for my internal use) (You can also skip unittest/ if you are not interested) doc/ folder contains a documentation that explains Mocker++ Code samples (unit test codes) are found in 'unittest/MockerppTest'

Cgreen has MOVED to GitHub: https://github.com/cgreen-devs/cgreen, files, documentation, source, issues are all there. This repo is OBSOLETE and not updated anymore. Cgreen is a unittesting and mocking framework for C and C++. Features include composite test suites, each test can be run in it's own process, trapping of hung tests, setup and teardown, extensible interface, support for mocking functions and automatic discovery of tests.

**** THIS LIBRARY WAS MOVED INTO Boost **** New location: https://github.com/boostorg/contract C++ Contract Programming (a.k.a. Design by Contract or DbC). All Eiffel features supported: subcontracting, postcondition old and result values, optional contract compilation, customizable action on assertion failure, block invariants, loop variants, etc. Plus virtual specifiers, concept checking, named parameters. See: http://contractpp.sourceforge.net

VSPMS is the "Very Simple Project Management System", which is a cross-platform set of shell tools and aliases to establish and share project environment variables, aliases, documentation, and setup procedures.

...The application expects as arguments one or more control files that consist of commands. Each line is interpreted and compared against a list of known commands. Comments must stay on their own line and should start with a # sign. The documentation uses the term target to refer to a program that is being tested. To create a new target use the TARGET command. To change current target use the SWITCH command. Targets are discarded only at the end of the program. If you do not check explicitly for program exit using END TARGET or EXIT CODE, the program will check this itself at the end. ...

JReq, or "Just Requirements", is a customizable requirements management application for the Linux platform.

Steel Rats is a gui wrapper for the command line source code auditing tool RATS. It examines C, Perl, php and python code for keywords that could cause security holes and provides a report for you to further investigate the possible security holes.

JPITools aims to provide tools to allow for improved documentation and APIs.

InPUT offers a descriptive and programming language independent format and IoC (Inversion of Control) container for the configuration and design of computer experiments. Code and more info can be found on github: http://github.com/feldob/InPUT