Legend:
Library
Module
Module type
Parameter
Class
Class type
Library
Module
Module type
Parameter
Class
Class type
package tezt
Legend:
Library
Module
Module type
Parameter
Class
Class type
Library
Module
Module type
Parameter
Class
Class type
Base test management (registering, initializations, etc).
include module type of struct include Tezt_core.Test end
Add a function to be called before each test start.
Used to reset counters such as the ones which are used to choose default process names.
val fail : ?__LOC__:string -> ('a, Format.formatter, unit, 'b) format4 -> 'aLog an error and stop the test right here.
If the optional location __LOC__ is provided, it is prepended to the error message. You would typically use it simply as Test.fail ~__LOC__ "..." to prepend location of the failure.
val register :
__FILE__:string ->
title:string ->
tags:string list ->
(unit -> unit Lwt.t) ->
unitRegister a test.
The __FILE__ argument, which should be equal to __FILE__ (i.e. just write Test.register ~__FILE__), is used to let the user select which files to run from the command-line.
One should be able to infer, from title, what the test will do. It is typically a short sentence like "addition is commutative" or "server runs until client tells it to stop".
The list of tags must be composed of short strings which are easy to type on the command line (lowercase letters, digits and underscores). Run the test executable with --list to get the list of tags which are already used by existing tests. Try to reuse them if possible.
The last argument is a function f which implements the test. If f needs to spawn external processes, it should use the Process module to do so, so that those processes are automatically killed at the end of the test. Similarly, if this function needs to create temporary files, it should declare them with Temp, and if it needs to have promises that run in the background, it should use Background.register (and not Lwt.async in particular).
If f raises an exception, act as if fail was called (without the error location unfortunately).
You can call register several times in the same executable if you want it to run several tests. Each of those tests should be standalone, as the user is able to specify the list of tests to run on the command-line.
The test is not actually run until you call run.
Get the current worker id.
In single-process mode (with -j 1), this always returns None.
In multi-process mode, this returns either:
None(if called in the scheduler process, i.e. outside of a test);- or
Some idwhere0 <= id < Cli.options.job_countand whereiduniquely identifies the current worker process that is running the current test.
Internals
The rest of this module is used by other modules of Tezt. You usually do not need to use it yourself.
Add a function to be called by run_with_scheduler before it does anything.
module type SCHEDULER = Tezt_core.Test.SCHEDULERval run_with_scheduler : (module SCHEDULER) -> unitGeneric function to run registered tests that should be run.
Depending on command-line options, this may do something else, such as printing the list of tests.
Instead of calling this directly, call Test.run, which is provided by the particular variant of Tezt you are using (Unix or JavaScript).
type t = Tezt_core.Test.tTest descriptions.
val get_test_by_title : string -> t optionGet a test by its title.
Return None if no test was registered with this title.
val run_one :
sleep:(float -> unit Lwt.t) ->
clean_up:(unit -> unit Lwt.t) ->
temp_start:(unit -> string) ->
temp_stop:(unit -> unit) ->
temp_clean_up:(unit -> unit) ->
t ->
Tezt_core.Log.test_result Lwt.tRun one test.
sleep is a function such as Lwt_unix.sleep or Lwt_js.sleep. It is used to implement timeouts.
clean_up is a function such as Process.clean_up (plus a wrapper to handle exceptions). It is ran at the end of the test.