wdio-teamcity-reporter-fork
v2.5.7
Published
WebdriverIO Teamcity reporter fork
Downloads
3
Readme
wdio-teamcity-reporter
WebdriverIO Teamcity reporter which makes it possible to display test results in real-time, makes test information available on the Tests tab of the Build Results page.
Installation
npm install wdio-teamcity-reporter --save-dev
Instructions on how to install WebdriverIO can be found here: http://webdriver.io/guide/getstarted/install.html
Configuration
Add reporter in your wdio.conf.js file:
exports.config = {
// ...
reporters: ['teamcity'],
reporterOptions: {
captureStandardOutput: false, // optional
flowId: true, // optional
message: '[title]', // optional
},
// ...
}
reporterOptions
reporterOptions
provide you a possibility to adjust reporter functionality.
captureStandardOutput (boolean)
— iftrue
, all the standard output (and standard error) messages received betweentestStarted
andtestFinished
messages will be considered test output. The default value isfalse
and assumes usage of testStdOut and testStdErr service messages to report the test output. Defaultfalse
.flowId (boolean)
— iftrue
,flowId
property will be added to all messages. Flow tracking is necessary for example to distinguish separate processes running in parallel. Defaulttrue
.message (string)
— possibility to provide particular format for the name property. Possible keys:[browser]
,[title]
. Example,[browser] / [title]
. Default[title]
.
Links
- Reference to the Teamcity documentation about reporting messages: https://confluence.jetbrains.com/display/TCD65/Build+Script+Interaction+with+TeamCity
- Teamcity testdrive: https://blog.jetbrains.com/teamcity/2019/08/getting-started-with-teamcity-testdrive/
License
The MIT License