Nothing
testPackage
. This is a convenience that has the same interface as tinytest::test_package()
but automatically convert the test results to JUnit.
It also has the following advantages compared to just calling tinytest::run_test_dir() |> writeJUnit()
:runTestDir
. This is a drop-in replacement for tinytest::run_test_dir()
. It is the work horse of
for the testPackage
function. It has the following features:tinytest
object in the result.tinytests2JUnit
containing additional metrics recorded during the test execution for use in the JUnit.For most users testPackage
will be the convenience one-liner funciton to add in your CI. While with
the runTestDir
you have full controll over which directories you want to call. This can be usefull
if you have multiple test stages written in tinytest.
file
of writeJUnit
now also accepts connection
object and now has a default argument stdout()
.When using testPackage
or the output of runTestDir
the following additional information is reported in the JUnit:
Note, it is still possible to use normal tinytests
results as returned by tinytest::run_test_dir()
with writeJUnit()
.
id
property filled in.info
attribute of a tinytest object. Any scripts or data that you put into this service are public.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.