You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The callback to `browserstackRunner.run` is called with two params -
45
-
1.`error`: This parameter is either `null` or an `Error` object (if test execution failed) with message as the reason of why executing the tests on `BrowserStack` failed.
46
-
2.`report`: This is an object which can be used to keep track of the `failed assertions` and the total count of `passed/failed` tests specific to a browser instance.
48
+
-`error`: This parameter is either `null` or an `Error` object (if test execution failed) with message as the reason of why executing the tests on `BrowserStack` failed.
49
+
-`report`: This is an array which can be used to keep track of the executed tests and suites in a run. Each object in the array has the following keys -
50
+
-`browser`: The name of the browser the test executed on.
51
+
-`tests`: An array of `Test` objects. The `Test` Objects are described [here](https://github.com/js-reporters/js-reporters#event-data)
52
+
-`suites`: A global Suite Object as described [here](https://github.com/js-reporters/js-reporters#event-data)
47
53
48
54
The structure of the `report` object is as follows -
0 commit comments