opened
runspired
username_0
Previous testem output:

```
ok 1 phantomjs - My Awesome Test Scenario
```

New Output

```
[12:31:30] ok 1 phantomjs - [50 ms] - My Awesome Test Scenario
```

Previous global timeout error message:

```
Browser exited on request from test driver
```

New global timeout error message

```
Test suite execution has timed out (config.timeout = 300 seconds). Terminated all test runners.
```
[FEAT BUGFIX] add test time and duration to TapReporter, fix double-exit check, print timeout error on exit if required
issue
created
runspired
username_0
cc @dcombslinkedin @username_1 @rwjblue
comment
created
stefanpenner
username_1
@username_0 have you confirmed this displays in the right place, in an actionable way? Specifically, would this have made your debugging session earlier this much better?
comment
created
runspired
username_0
<img width="930" alt="screen shot 2018-08-02 at 2 12 01 pm" src="https://user-images.githubusercontent.com/650309/43611481-1804eb96-965e-11e8-9185-c65ec1a4c29a.png">

@username_1 there may be more we could do but this definitely would have been a nice start :)
comment
created
stefanpenner
username_1
released as v2.9.1 :tada:
comment
created
kategengler
username_2
This tells whether the test point passed or failed. **It must be at the beginning of the line**. /^not ok/ indicates a failed test point. /^ok/ is a successful test point. This is the only mandatory part of the line. Note that unlike the Directives below, ok and not ok are case-sensitive. (emphasis added)

I suspect this will break various tools that use TAP output.
comment
created
runspired
username_0
#1284 exists to rectify this
comment
created
kategengler
username_2
@username_0 I think the time in that location is fine (it would count as part of the test description, but so does `phantomjs`).
comment