box / box/leche

wdio-teamcity-reporter issue

Open
#27 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
102
Forks
1
PR merge metrics
No merged PRs in 30d

Description

I use leche to run 4 mocha test cases in one context file, with 2 data rows specified as named data properties. So there is one file, containing a context ("Test suite"), then a withData declaration with 2 data rows:

'demo1 user': [{username: nfglskdngl
'demo2 user':...
...

Below that there are 4 test cases with are intended to run with 2 different users, so 8 test results are expeced.

Test results are printed very well using spec reporter (I use webdriver.io test runner and the reporter is therefore set in conf.js).

On teamcity I use another configuration file, and specifically a teamcity reporter (wdio-teamcity-reporter in npm repository). The results produced with the setup above do not come out right. Instead of the expected 8 test results, I see the very first test case coming out right with the data context :
- Test suite xx with demo1 user It can ...

The other test cases in the file (below the first one) are coming out without the context and data annotation, and thus are grouped by Teamcity in one row (market in status as 2 runs).
- OK (2 runs) It can...

So teamcity does indeed run the 8 cases using withData, but the results are produced in a less-readable manner. I would like to determine: is that an issue in leche or in the wdio-teamcity-reporter?? Thanks in advance

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the four Mocha cases with two named data rows in the leche context, using the separate conf.js configuration with wdio-teamcity-reporter. Compare the TeamCity output with the spec reporter output and trace whether the missing context and data annotations originate in leche or the reporter. Done means identifying the responsible component and documenting or correcting the output so all eight results retain their annotations.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.