JUnit Formatter v2.2.0 JUnitFormatter View Source

  • A ExUnit.Formatter implementation that generates a xml in the format understood by JUnit.

To acomplish this, there are some mappings that are not straight one to one. Therefore, here goes the mapping:

  • JUnit - ExUnit
  • Testsuites - :testsuite
  • Testsuite - %ExUnit.TestCase{}
  • failures = failures
  • skipped = skip
  • errors = invalid
  • time = (sum of all times in seconds rounded down)
  • Testcase - %ExUnit.Test
  • name = :case
  • test = :test
  • content (only if not successful)
  • skipped = {:state, {:skip, _}}
  • failed = {:state, {:failed, {_, reason, stacktrace}}}
  • reason = reason.message
  • contet = Exception.format_stacktrace(stacktrace)
  • error = {:invalid, module}

The report is written to a file in the _build directory.

Link to this section Summary

Functions

Formats time from nanos to seconds

Helper function to get the full path of the generated report file. It can be passed 2 configurations

  • report_dir: full path of a directory (defaults to Mix.Project.app_path())
  • report_file: name of the generated file (defaults to “test-junit-report.xml”)

Invoked when the server is started. start_link/3 or start/3 will block until it returns

Link to this section Functions

Link to this function format_time(time) View Source
format_time(integer()) :: integer()

Formats time from nanos to seconds

Link to this function get_report_file_path() View Source
get_report_file_path() :: String.t()

Helper function to get the full path of the generated report file. It can be passed 2 configurations

  • report_dir: full path of a directory (defaults to Mix.Project.app_path())
  • report_file: name of the generated file (defaults to “test-junit-report.xml”)

Invoked when the server is started. start_link/3 or start/3 will block until it returns.

args is the argument term (second argument) passed to start_link/3.

Returning {:ok, state} will cause start_link/3 to return {:ok, pid} and the process to enter its loop.

Returning {:ok, state, timeout} is similar to {:ok, state} except handle_info(:timeout, state) will be called after timeout milliseconds if no messages are received within the timeout.

Returning {:ok, state, :hibernate} is similar to {:ok, state} except the process is hibernated before entering the loop. See c:handle_call/3 for more information on hibernation.

Returning :ignore will cause start_link/3 to return :ignore and the process will exit normally without entering the loop or calling c:terminate/2. If used when part of a supervision tree the parent supervisor will not fail to start nor immediately try to restart the GenServer. The remainder of the supervision tree will be (re)started and so the GenServer should not be required by other processes. It can be started later with Supervisor.restart_child/2 as the child specification is saved in the parent supervisor. The main use cases for this are:

  • The GenServer is disabled by configuration but might be enabled later.
  • An error occurred and it will be handled by a different mechanism than the Supervisor. Likely this approach involves calling Supervisor.restart_child/2 after a delay to attempt a restart.

Returning {:stop, reason} will cause start_link/3 to return {:error, reason} and the process to exit with reason reason without entering the loop or calling c:terminate/2.

Callback implementation for GenServer.init/1.

Link to this macro xmlAttribute(args \\ []) View Source (macro)
Link to this macro xmlAttribute(record, args) View Source (macro)
Link to this macro xmlElement(args \\ []) View Source (macro)
Link to this macro xmlElement(record, args) View Source (macro)
Link to this macro xmlText(args \\ []) View Source (macro)
Link to this macro xmlText(record, args) View Source (macro)