Search Results for "output" - Page 4

STDL (Structured test description language) is a domain-specific testing language that is used to auto-generate unit test code. It supports a myriad of output languages (incl. C#). The project's aim is that of reducing the resources required for testing

FakeSMTPServer is a solution for testing web-based products that require a "unique" email address. Instead of being a "real" smtp server, this server forwards all email to a single email address, or can output them to the console instead.

A Perl script that, given the output of the Firefox extension Live HTTP Headers, will replay the script using Test::WWW::Mechanize.

maven2-junit4x is a maven2 plug-in which runs test written in Junit4.x. It has customisable output options and is written to make as few a demands on the developer as possible.

dLog is a swift c++ std::stream based output logger that works with tags. It is easy to use, swift and inexpensive when turned off. An example: dLog::write("fileOutput") << "open file:" << filename;

BasicXSLT has a new home on GitHub at: https://github.com/evanspa/BasicXSLT ------------------------------------------------------------- Java-based tool for performing XSL transformations. Allows for multiple XSL stylesheets to be chained together and allows for parameters and output properties to be set on each stylesheet. Remembers configuration information and provides timing numbers.

wxPyCoverage accepts trace.py output and displays the Python source code, indicating lines not yet executed.

...It has to be walked through your web-site once, it can then follow the same steps and report whether the pages did not work as expected. Variable values as well as HTML output can be tested.

1337writer is a converter for 'normal' text to 1337 / l33t text (leetspeech). simply input your text and the programm will output the 1337 version. (hardcore 1337 or simple 1337).

A simple, robust, easy to use C++ unit testing framework. The output is being integrated with doxygen for automatic results reporting as well.

Experior doesn't care what language your test program is written in. All it cares about is that each test's output begins and ends with a simple line of JSON. Your test program can validate its own output, in which case Experior just acts as a report engine. Alternatively -- or additionally -- you can write validation functions in JavaScript, and Experior will run them against the test output. Finally, Experior can compare your current test output against a copy of previous test output and alert you to regressions.

Converting Fit tests automatically to JUnit tests while running. Simply add to your test suite: suite.addTest(FitlessTestStarterSuite.suiteFit("fit/html/input", "fit/output")); You do not need Fitnesse, because your fit tests run in JUnit directly.

...Currently, AutoBlocks can run various configurations of pre-built blocks/classes/scripts and can be tried with Selenium 1 or 2, which is configurable via the properties file. The framework is still in the works and needs things like telemetry and appropriate input/output data structures for the tests.

The BP-Tools set consist from applications supporting EFT testing, benchmarking and transaction service development. BP-Tools suite currently consists of following three components: - BP-CCALC: Cryptographic Calculator - BP-CardEdit: Thales P3 Input/Output file editor - BP-EMVT: EMV Tool - BP-HCMD: Thales HSM Commander