Erlang -- Test Server Application

User's Guide
Reference Manual
Release Notes
PDF
Top

Test Server
Reference Manual
Version 3.10

Expand All
Contract All

Table of Contents

- test_server (App)
- test_server_ctrl
  - Top of manual page
  - start/0
  - stop/0
  - add_dir/2
  - add_dir/3
  - add_dir/2
  - add_dir/3
  - add_module/1
  - add_module/2
  - add_case/2
  - add_case/3
  - add_cases/2
  - add_cases/3
  - add_spec/1
  - add_dir_with_skip/3
  - add_dir_with_skip/4
  - add_module_with_skip/2
  - add_module_with_skip/3
  - add_case_with_skip/3
  - add_case_with_skip/4
  - add_cases_with_skip/3
  - add_cases_with_skip/4
  - add_tests_with_skip/3
  - abort_current_testcase/1
  - set_levels/3
  - get_levels/0
  - jobs/0
  - multiply_timetraps/1
  - scale_timetraps/1
  - get_timetrap_parameters/0
  - cover/2
  - cover/2
  - cover/3
  - cross_cover_analyse/2
  - trc/1
  - stop_trace/0
  - run_test/1
  - get_suite/2
  - init_tc/3
  - end_tc/3
  - report/2
  - error_notification/4
  - warn/1
  - target_info/0
- test_server
  - Top of manual page
  - os_type/0
  - fail/0
  - fail/1
  - timetrap/1
  - timetrap_cancel/1
  - timetrap_scale_factor/0
  - sleep/1
  - adjusted_sleep/1
  - hours/1
  - minutes/1
  - seconds/1
  - format/1
  - format/2
  - format/2
  - format/3
  - capture_start/0
  - capture_stop/0
  - capture_get/0
  - messages_get/0
  - timecall/3
  - do_times/4
  - do_times/2
  - m_out_of_n/3
  - call_crash/3
  - call_crash/4
  - call_crash/5
  - temp_name/1
  - break/1
  - continue/0
  - run_on_shielded_node/2
  - start_node/3
  - stop_node/1
  - is_commercial/0
  - is_release_available/1
  - is_native/1
  - app_test/1
  - app_test/2
  - appup_test/1
  - comment/1
  - all/1
  - init_per_suite/1
  - end_per_suite/1
  - init_per_testcase/2
  - end_per_testcase/2
  - Case/1
  - Case/1
  - Case/1

# test_server

### APPLICATION

test_server

### APPLICATION SUMMARY

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 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
- 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 information.

### Configuration

There are currently no configuration parameters available for this application.

### SEE ALSO