In the Combined Report, the capabilities section needs to be moved from the "header" because it does not work when multiple capabilities are provided.
The question of where to put the capabilities depends on what you fundamentally consider a unique test suite? One could argue that since WDIO spawns suites for each set of capabilities the reporting should live at the SUITE level. Since we do not define a new set of tests in our code for each Browser / OS combination I am inclined to report the capabilities at the TEST level. The "experiment" is the test + browser + os + other capabilities...
However, in an effort to keep the JSON file size from exploding it probably makes most sense to report the capabilities at the suite level.
fijijavis
commented
5 years ago
In the Combined Report, the capabilities section needs to be moved from the "header" because it does not work when multiple capabilities are provided.
The question of where to put the capabilities depends on what you fundamentally consider a unique test suite? One could argue that since WDIO spawns suites for each set of capabilities the reporting should live at the SUITE level. Since we do not define a new set of tests in our code for each Browser / OS combination I am inclined to report the capabilities at the TEST level. The "experiment" is the test + browser + os + other capabilities...
However, in an effort to keep the JSON file size from exploding it probably makes most sense to report the capabilities at the suite level.