114
26%
master: 25%

Ran 16 Nov 2016 10:34PM UTC

Jobs 1

Files 48

Run time 3s

Badge

Embed ▾

pending completion

Build # 114

Build Type

push

travis-ci

Committed by

okurz

Commit Message

Use Carp for more helpful caller context in testapi

Instead of the pretty useless information that a command died in testapi.pm at
a certain line the test should give information which line in the test code
caused a test failure.

E.g. instead of

```
22:06:58.3323 28950 >>> testapi::wait_serial: OZvtF-\d+-: fail
22:06:58.3323 28950 # Test died:
command 'foo' failed: died here at ../../testapi.pm line 627.
```

you now get

```
22:12:21.4122 588 >>> testapi::wait_serial: OZvtF-\d+-: fail
22:12:21.4125 588 # Test died: command 'foo' failed: died here at /var/lib/openqa/share/tests/opensuse/tests/boot/boot_to_desktop.pm line 21.

```

for an `assert_script_run` with the corresponding 'fail_message'.
Same or similar output can not be expected for other functions, too, e.g.
shutdown, select_console, etc.

Also in 'runtest' and 'run_post_fail' the unnecessary warn telling about the
`run_post_fail` call from within basetest.pm is removed as well as redundant
newlines. ONe line break after the message should be enough. We should not
need 2 additional blank lines.

Run Details

1303 of 4941 relevant lines covered (26.37%)

5.66 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	114.1	16 Nov 2016 10:34PM UTC	48	26.37	Travis Job 114.1

Source Files on build 114

Coverage	∆	File	Lines	Relevant	Covered	Missed	Hits/Line

okurz / os-autoinst / 114
26%
master: 25%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 114

okurz / os-autoinst / 114 26% master: 25%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 114

okurz / os-autoinst / 114
26%
master: 25%

README BADGES
x