Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

test_server(7) [linux man page]

test_server(7)						   Erlang Application Definition					    test_server(7)

NAME
test_server - Test Server for manual or automatic testing of Erlang code DESCRIPTION
Test Server is a portable test server for automated application testing. The server can run test suites on local or remote targets and log progress and results to HTML pages. The main purpose of Test Server is to act as engine inside customized test tools. A callback interface for such framework applications is provided. In brief the test server supports: * Running multiple, concurrent test suites * Running tests on remote and even diskless targets * Test suites may contain other test suites, in a tree fashion * Logging of the events in a test suite, on both suite and case levels * HTML presentation of test suite results * HTML presentation of test suite code * Support for test suite authors, e.g. start/stop slave nodes * Call trace on target and slave nodes For information about how to write test cases and test suites, please see the Test Server User's Guide and the reference manual for the test_server module. Common Test is an existing test tool application based on the OTP Test Server. Please read the Common Test User's Guide for more informa- tion. CONFIGURATION
There are currently no configuration parameters available for this application. SEE ALSO
Ericsson AB test_server 3.4.3 test_server(7)

Check Out this Related Man Page

App::Prove::State::Result::Test(3pm)			 Perl Programmers Reference Guide		      App::Prove::State::Result::Test(3pm)

NAME
App::Prove::State::Result::Test - Individual test results. VERSION
Version 3.26 DESCRIPTION
The "prove" command supports a "--state" option that instructs it to store persistent state across runs. This module encapsulates the results for a single test. SYNOPSIS
# Re-run failed tests $ prove --state=fail,save -rbv METHODS
Class Methods "new" Instance Methods "name" The name of the test. Usually a filename. "elapsed" The total elapsed times the test took to run, in seconds from the epoch.. "generation" The number for the "generation" of the test run. The first generation is 1 (one) and subsequent generations are 2, 3, etc. "last_pass_time" The last time the test program passed, in seconds from the epoch. Returns "undef" if the program has never passed. "last_fail_time" The last time the test suite failed, in seconds from the epoch. Returns "undef" if the program has never failed. "mtime" Returns the mtime of the test, in seconds from the epoch. "raw" Returns a hashref of raw test data, suitable for serialization by YAML. "result" Currently, whether or not the test suite passed with no 'problems' (such as TODO passed). "run_time" The total time it took for the test to run, in seconds. If "Time::HiRes" is available, it will have finer granularity. "num_todo" The number of tests with TODO directives. "sequence" The order in which this test was run for the given test suite result. "total_passes" The number of times the test has passed. "total_failures" The number of times the test has failed. "parser" The underlying parser object. This is useful if you need the full information for the test program. perl v5.18.2 2014-01-06 App::Prove::State::Result::Test(3pm)
Man Page