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
log.debug(<spanclass="string"><spanclass="delimiter">"</span><spanclass="content">Recording available at {}</span><spanclass="delimiter">"</span></span>, recordingPath);
1977
+
1978
+
<spanclass="comment">// Get recording as base64</span>
<p>As of version 6.3.0, Selenium-Jupiter provides built-in reporting capabilities through <ahref="https://extentreports.com/">ExtentReports</a>. This feature is enabled out of the box. All the tests executed with Selenium-Jupiter in the same suite will be reported (passed, skipped, failed) in a single HTML report per test suite execution. In addition, all the video recordings, both using <code>@DockerBrowser</code> and <code>@Watch</code>, will be gathered by Selenium-Jupiter and added to the resulting report (internally, the videos are encoded as Base64 in the HTML report), for example:</p>
2328
+
</div>
2329
+
<divclass="imageblock thumb">
2330
+
<divclass="content">
2331
+
<imgsrc="img/selenium-jupiter-report-example-1.png" alt="selenium jupiter report example 1">
2332
+
</div>
2333
+
<divclass="title">Figure 5. Test report with embedded recording</div>
2334
+
</div>
2335
+
<divclass="paragraph">
2336
+
<p>Finally, when a test fails, Selenium-Jupiter will gather two troubleshooting resources from the browser. First, it will try to take a screenshot of the browser (if it is still available). Second, it will try to gather the browser console logs, if possible. The screenshot(s) and the log(s) are automatically added for failed tests, for example:</p>
2337
+
</div>
2338
+
<divclass="imageblock thumb">
2339
+
<divclass="content">
2340
+
<imgsrc="img/selenium-jupiter-report-example-2.png" alt="selenium jupiter report example 2">
2341
+
</div>
2342
+
<divclass="title">Figure 6. Test report with gathered screenshots and browser console logs</div>
2343
+
</div>
2344
+
<divclass="paragraph">
2345
+
<p>You can find a complete HTML report example in this <ahref="reports/selenium-jupiter-20250902-150317.html">link</a>.</p>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Output folder for recordings and screenshots. This key accepts the special value <code>surefire-reports</code> for the <ahref="#integration-with-jenkins">integration with Jenkins</a>. In case of the special value <code>surefire-reports</code> there will <strong>always</strong> be a separate output folder per class (see below, <code>setOutputFolderPerClass(boolean)</code>).</p></td>
2427
+
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">Output folder for recordings, screenshots, and reports. This key accepts the special value <code>surefire-reports</code> for the <ahref="#integration-with-jenkins">integration with Jenkins</a>. In case of the special value <code>surefire-reports</code> there will <strong>always</strong> be a separate output folder per class (see below, <code>setOutputFolderPerClass(boolean)</code>).</p></td>
<tdclass="tableblock halign-left valign-top"><pclass="tableblock">File name for the HTML report created in each test suite execution. If the <code>{date}</code> placeholder is used in this name, the system timestamp is added. By default, this file is created in the current folder (see previous configuration key).</p></td>
0 commit comments