passes: 206

failures: 0

pending: 0

other: 0

duration: 1 sec, 915 ms, 165 μs, and 2 hnsecs

trial.reporters.xunit 1 ms, 431 μs, and 9 hnsecs

XUnitTestXml should transform a success test
success 36 μs and 1 hnsec
XUnitTestXml should transform an empty suite
success 75 μs and 9 hnsecs
XUnitTestXml should transform a suite with a skipped test
success 66 μs and 8 hnsecs
XUnitTestXml should transform a suite with a unknown test
success 73 μs and 9 hnsecs
XUnitTestXml should transform a failing test
success 39 μs and 5 hnsecs
XUnitTestXml should transform a suite with a failed test
success 65 μs
XUnitTestXml should transform a suite with a success test
success 61 μs and 1 hnsec

trial.settings 364 μs and 8 hnsecs

it should be able to compile the settings code
success 1 μs and 3 hnsecs
it should be able to transform the Settings to code.
success 70 μs and 8 hnsecs

trial.reporters.list 521 μs and 3 hnsecs

it should print two failing tests
success 43 μs and 3 hnsecs
it should print a sucess test
success 37 μs and 3 hnsecs
it should print a pending test
success 32 μs and 6 hnsecs

trial.reporters.specprogress 1 sec, 849 μs, and 8 hnsecs

it should print a success test
success 1 sec, 260 μs, and 9 hnsecs
it should print two success tests
success 328 μs and 8 hnsecs

trial.discovery.testclass 7 ms, 268 μs, and 6 hnsecs

methodCaller should call the method with custom random generators
success 29 μs and 1 hnsec
TestClassDiscovery should execute tests from a Test Suite class
success 33 μs and 2 hnsecs
TestClassDiscovery should find the Test Suite class
success 51 μs and 1 hnsec
discoverTestCases should find the Test Suite class
success 2 ms, 950 μs, and 4 hnsecs
TestClassDiscovery should execute the before and after methods tests from a Test Suite class
success 85 μs and 5 hnsecs
methodCaller should call the method with random numeric values
success 54 μs and 6 hnsecs
discoverTestCases should find the same tests like testCases
success 3 ms, 80 μs, and 8 hnsecs

trial.interfaces 29 ms, 906 μs, and 5 hnsecs

Attach the readme file
success 2 μs and 6 hnsecs
A suite runner should run a success test case and add it to the result
success 167 μs and 3 hnsecs
A suite runner should call the suite lifecycle listener methods
success 433 μs and 2 hnsecs
A suite runner should set the data to an empty suite runner
success 9 μs and 4 hnsecs
Label string representation should be in Json format
success 10 μs and 8 hnsecs
A test runner should call the test listeners in the right order
success 121 μs and 5 hnsecs
A suite runner should run a failing test case and add it to the result
success 27 ms and 575 μs
A test runner should add the steps to the report
success 163 μs and 4 hnsecs
TestCase string representation should be a JSON string
success 33 μs and 5 hnsecs
SourceLocation string representation should be a JSON string
success 11 μs and 8 hnsecs
Convert a test case to test result
success 132 μs and 6 hnsecs

trial.runner 819 μs and 1 hnsec

it should have an empty key for items that contain both values and childs
success 49 μs and 9 hnsecs
It should return true if all the tests succeded
success 8 μs and 1 hnsec
It should return false if one the tests failed
success 8 μs
convert an assoc array to JSON hierarchy
success 39 μs and 9 hnsecs
describeTests should return the tests cases serialised in json format
success 31 μs and 5 hnsecs
It should return the name of this test
success 10 μs and 9 hnsecs
It should return true for an empty result
success 5 μs and 5 hnsecs

trial.stackresult 29 ms, 324 μs, and 5 hnsecs

Get an external function frame info from linux format
success 637 μs and 3 hnsecs
The frame should not print the module if it's missing
success 12 μs and 5 hnsecs
Get frame info from windows platform format with path
success 107 μs and 3 hnsecs
Get frame info from CRuntime_Glibc format without offset
success 111 μs and 6 hnsecs
Get the main frame info from linux format
success 159 μs and 1 hnsec
It should detect external functions
success 40 μs and 5 hnsecs
Get an external function frame info from linux format
success 232 μs and 5 hnsecs
Get frame info from NetBSD format
success 146 μs and 2 hnsecs
Get frame info from windows platform format without path
success 98 μs and 2 hnsecs
Get an missing info function frame info from linux format
success 185 μs
The frame should not output the file if it is missing from the stack
success 18 μs and 9 hnsecs
The frame should not print the file if it's missing
success 14 μs and 8 hnsecs
The frame should print all fields
success 21 μs and 7 hnsecs
The frame should not print an index < 0 or a line < 0
success 22 μs and 7 hnsecs
Get frame info from CRuntime_Glibc format with offset
success 126 μs and 3 hnsecs
Get frame info from Darwin platform format
success 82 μs and 3 hnsecs
toTestException should convert an Exception from the current project to a TestException with 2 reporters
success 6 ms, 273 μs, and 6 hnsecs
The frame should display `????` when the name is missing
success 16 μs
The stack result should display the stack in a readable form
success 17 ms, 154 μs, and 4 hnsecs
The frame should not print the offset if it's missing
success 19 μs and 7 hnsecs
The frame should not output an index < 0 or a line < 0
success 24 μs and 1 hnsec
The frame should not output the module if it is missing from the stack
success 11 μs and 5 hnsecs
Get a function frame info from linux format
success 320 μs and 4 hnsecs
toTestException should convert an Exception from other project to a TestException with 1 reporter
success 56 μs and 7 hnsecs
The frame should print ???? when the name is missing
success 11 μs and 5 hnsecs
The frame should convert a frame to string
success 29 μs and 1 hnsec
The message of a wrapped exception should contain the original exception
success 28 μs and 3 hnsecs
The frame should not output the offset if it is missing from the stack
success 15 μs and 7 hnsecs

trial.reporters.allure 3 ms, 854 μs, and 8 hnsecs

AllureTestXml should add the attachments
success 476 μs
AllureSuiteXml should transform an empty suite
success 99 μs and 6 hnsecs
AllureTestXml should transform a failing test
success 79 μs and 9 hnsecs
AllureSuiteXml should add the attachments
success 313 μs
AllureTestXml should transform a test with labels
success 46 μs
Allure attachments should be copied to a folder containing the suite name
success 387 μs and 5 hnsecs
AllureStepXml should transform nested steps
success 83 μs and 2 hnsecs
AllureTestXml should transform a success test
success 28 μs and 3 hnsecs
AllureStepXml should transform a step
success 25 μs and 8 hnsecs
Allure attachments should avoid name collisions
success 380 μs and 8 hnsecs
AllureStepXml should add the attachments
success 309 μs and 8 hnsecs
AllureTestXml should transform a test with steps
success 95 μs and 3 hnsecs
AllureSuiteXml should transform a suite with a success test
success 58 μs and 8 hnsecs

trial.reporters.landing 1 ms, 605 μs, and 8 hnsecs

it should print 10 success tests
success 1 ms and 451 μs

trial.executor.parallel 717 ms, 727 μs, and 9 hnsecs

it should run the tests in parallel
success 102 ms, 464 μs, and 3 hnsecs
it should call update() many times
success 102 ms, 74 μs, and 5 hnsecs
A parallel executor should call the events in the right order
success 202 ms, 531 μs, and 8 hnsecs
A parallel executor should get the result of a failing test
success 2 ms, 245 μs, and 5 hnsecs
it should be able to limit the parallel tests number
success 205 ms, 497 μs, and 7 hnsecs
A parallel executor should get the result of a success test
success 101 ms, 855 μs, and 8 hnsecs

trial.reporters.result 1 ms, 218 μs, and 8 hnsecs

The user should be notified with a message when no test is present
success 41 μs and 3 hnsecs
The user should see the number of suites and tests when multiple tests are run
success 40 μs
The user should see the number if there is a pending test
success 66 μs and 5 hnsecs
The user should see the reason of a failing test
success 92 μs and 6 hnsecs
The user should see the number if there are more than one pending tests
success 54 μs and 1 hnsec
The user should see a nice message when one test is run
success 31 μs and 9 hnsecs

trial.executor.single 1 ms, 778 μs, and 4 hnsecs

Executing a test case that throws a PendingTestException should mark the test result as pending instead of a failure
success 46 μs and 1 hnsec
Executing a test case should set the right begin and end times
success 1 ms, 288 μs, and 5 hnsecs

trial.coverage 6 ms, 18 μs, and 5 hnsecs

It should return false for when the ignore coverage file is missing
success 145 μs and 3 hnsecs
Check project paths
success 38 μs and 7 hnsecs
It should get the filename from the .lst file with no coverage
success 25 μs and 1 hnsec
Check variables for the coverage header
success 126 μs and 8 hnsecs
check a 50% external covered file
success 28 μs and 5 hnsecs
It should return true for ignored coverage files
success 184 μs and 2 hnsecs
should mark the `trial_.d` file as external file
success 104 μs and 3 hnsecs
It should get the filename from the .lst file with percentage
success 25 μs
Check if the table body is inserted
success 31 μs and 9 hnsecs
should replace the variables inside the page.html
success 62 μs and 9 hnsecs
It should get the filename from the .lst file with no coverage
success 21 μs and 6 hnsecs
No files are always 100% covered
success 17 μs and 1 hnsec
It should get the filename from the .lst file with no code
success 20 μs and 5 hnsecs
check a 50% covered file
success 33 μs and 3 hnsecs
It should get the filename from the .lst file with no code
success 15 μs and 1 hnsec
Check variables for the coverage html
success 439 μs and 7 hnsecs
It should parse an empty line
success 30 μs and 2 hnsecs
Render line coverage column
success 192 μs and 3 hnsecs
The line coverage shield should contain the percent
success 62 μs and 6 hnsecs
It should get the coverage summary from the .lst file with missing data
success 14 μs and 4 hnsecs
It should get the filename from the .lst file with percentage
success 22 μs and 8 hnsecs
should convert a .lst file to CoveredFile structure
success 269 μs and 5 hnsecs
It should get the coverage summary from the .lst file with no coverage
success 23 μs and 8 hnsecs
It should replace a variable inside a page
success 14 μs and 4 hnsecs
should replace the variables inside the page.html
success 126 μs and 2 hnsecs
It should convert a .lst file to covered line structs
success 121 μs and 8 hnsecs
It should get the coverage summary from the .lst file with percentage
success 23 μs and 1 hnsec

trial.reporters.stats 1 ms, 949 μs, and 3 hnsecs

it should add steps to the storage
success 273 μs and 3 hnsecs
it should add suite to the storage
success 208 μs and 5 hnsecs
it should convert stat storage to csv
success 77 μs and 4 hnsecs
It should write the stats to the expected path
success 109 μs and 1 hnsec
it should create stat storage from csv
success 232 μs and 9 hnsecs
it should add tests to the storage
success 188 μs and 3 hnsecs

trial.reporters.dotmatrix 483 μs and 4 hnsecs

it should print a success test
success 28 μs and 8 hnsecs
it should print a failing test
success 27 μs and 1 hnsec
it should print a pending test
success 26 μs and 7 hnsecs

trial.discovery.unit 93 ms, 184 μs, and 1 hnsec

The discoverTestCases should find this test
success 4 ms, 808 μs, and 9 hnsecs
The discoverTestCases should find the test with the flaky attribute
success 4 ms, 916 μs, and 9 hnsecs
__unittest_lifecycle_trial_discovery_unit_d_718_12()
success 3 ms, 697 μs, and 3 hnsecs
It should find this flaky test
success 12 ms and 323 μs
The discoverTestCases should find the test with issues attributes
success 3 ms, 660 μs, and 6 hnsecs
clearCommentTokens should remove comment tokens
success 45 μs and 5 hnsecs
It should find this test with issues attributes
success 12 ms and 792 μs
It should find this test
success 12 ms, 532 μs, and 4 hnsecs
It should find the line of this test
success 12 ms, 247 μs, and 6 hnsecs
It should group comments
success 139 μs and 6 hnsecs
The discoverTestCases should find the test with the string attribute name
success 3 ms, 870 μs, and 5 hnsecs
check comment types
success 40 μs and 8 hnsecs
discoverTestCases should find the same tests like testCases
success 16 ms and 690 μs
discoverTestCases should ignore version(unittest)
success 3 ms, 526 μs, and 6 hnsecs

trial.reporters.html 1 ms, 849 μs, and 8 hnsecs

it should print a pending test
success 429 μs and 8 hnsecs
it should print a success test
success 568 μs and 7 hnsecs
it should print a failure test
success 450 μs and 4 hnsecs

trial.reporters.progress 338 μs and 1 hnsec

it should print 10 success tests
success 152 μs and 3 hnsecs

trial.reporters.specsteps 1 ms, 59 μs, and 3 hnsecs

it should print the duration of a long test
success 91 μs and 1 hnsec
it should format the steps for a failing test
success 223 μs and 5 hnsecs
it should format the steps for a success test
success 241 μs and 3 hnsecs
it should format a pending test
success 65 μs

trial.reporters.spec 1 ms, 70 μs, and 4 hnsecs

it should split suites by dot
success 87 μs and 5 hnsecs
it should omit the common suite names
success 109 μs and 6 hnsecs
it should print a pending test
success 43 μs and 5 hnsecs
it should print a success test
success 43 μs and 7 hnsecs
it should print a failing test
success 40 μs and 4 hnsecs
it should print the test duration
success 74 μs and 7 hnsecs
it should print two success tests
success 86 μs and 1 hnsec

trial.reporters.tap 893 μs and 2 hnsecs

it should print the results of a TestException
success 138 μs and 4 hnsecs
it should not print the YAML if the throwable is missing
success 17 μs
it should print a failing test with a basic throwable
success 92 μs and 1 hnsec
it should print "The Plan" at the beginning
success 30 μs and 6 hnsecs
it should print a sucess test
success 25 μs and 5 hnsecs

trial.reporters.writer 1 ms, 36 μs, and 8 hnsecs

Buffered writer should keep the old line char position
success 26 μs and 8 hnsecs
Buffered writer should print text and add a new line
success 15 μs
Buffered writer should print text and a new line
success 12 μs and 9 hnsecs
Buffered writer should go back 1 line
success 17 μs and 9 hnsecs
Buffered writer should not replace a line if the new text is shorter
success 27 μs
Buffered writer should return an empty buffer
success 8 μs
Buffered writer should keep the old line number
success 19 μs and 7 hnsecs
Buffered writer should print text
success 15 μs and 8 hnsecs

trial.discovery.spec 6 ms, 619 μs, and 4 hnsecs

getTestCases should find the spec suite
success 23 μs
It should execute the spec before hooks
success 32 μs and 8 hnsecs
resolve the string tokens
success 22 μs and 2 hnsecs
discoverTestCases should find the same tests like testCases
success 2 ms, 699 μs, and 5 hnsecs
getTestCases should find the spec suite
success 21 μs and 6 hnsecs
getTestCases should find nested spec suites
success 292 μs and 1 hnsec
It should execute the spec after all hooks
success 40 μs and 9 hnsecs
It should execute the spec before all hooks
success 37 μs and 1 hnsec
discoverTestCases should find the spec suite
success 2 ms, 271 μs, and 8 hnsecs
It should execute the spec after hooks
success 36 μs and 1 hnsec

trial.reporters.visualtrial 1 ms, 35 μs, and 7 hnsecs

it should print the results of a TestException
success 135 μs and 3 hnsecs
it should print "The Plan" at the beginning
success 25 μs and 3 hnsecs
it should print the test location
success 66 μs and 3 hnsecs
it should print a failing test with a basic throwable
success 65 μs and 8 hnsecs
it should print a sucess test
success 20 μs and 3 hnsecs
it should not print the YAML if the throwable is missing
success 22 μs

trial.discovery.spec.Algorithm 217 μs and 7 hnsecs

should return false when the value is not present
success 8 μs and 8 hnsecs

trial.discovery.spec.Nested describes.level 1.level 2 286 μs and 6 hnsecs

test name
success 3 μs and 2 hnsecs

trial.discovery.spec.Nested describes.other level 1.level 2 238 μs and 6 hnsecs

test name
success 5 μs and 1 hnsec

trial.discovery.spec.Before all.level 2 330 μs and 2 hnsecs

should run the hooks
success 4 μs and 6 hnsecs
should run the hooks
success 4 μs and 5 hnsecs

trial.discovery.spec.Before all.level 2 bis 173 μs and 5 hnsecs

should run the hooks
success 4 μs and 1 hnsec

trial.discovery.spec.Before each 172 μs and 5 hnsecs

should run the hooks
success 3 μs and 8 hnsecs

trial.discovery.spec.Before each.level 2 176 μs and 1 hnsec

should run the hooks
success 4 μs and 9 hnsecs

trial.discovery.spec.Before each.level 2 bis 138 μs and 2 hnsecs

should run the hooks
success 3 μs

trial.discovery.spec.After all.level 2 313 μs and 3 hnsecs

should run the hooks
success 4 μs and 2 hnsecs
should run the hooks
success 2 μs and 8 hnsecs

trial.discovery.spec.After all.level 2 bis 180 μs and 8 hnsecs

should run the hooks
success 2 μs and 8 hnsecs

trial.discovery.spec.After each 156 μs and 9 hnsecs

should run the hooks
success 3 μs and 5 hnsecs

trial.discovery.spec.After each.level 2 177 μs

should run the hooks
success 4 μs and 5 hnsecs

trial.discovery.spec.After each.level 2 bis 188 μs and 4 hnsecs

should run the hooks
success 5 μs and 1 hnsec

trial.discovery.testclass.SomeTestSuite 205 μs

A simple test
success 7 μs and 1 hnsec

trial.discovery.testclass.OtherTestSuite 2 hnsecs

Some other name
success 10 μs and 7 hnsecs