Date: Thu, 28 Mar 2024 15:04:19 +0000 (UTC) Message-ID: <1470710352.10323.1711638259231@docs.getxray.app> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_10322_777249767.1711638259231" ------=_Part_10322_777249767.1711638259231 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Sometimes, you may start with a "manual" test (i.e. test composed = of steps executed manually) and later on implement an automated variant of = it, using Selenium on top of an automation framework (e.g. TestNG, Junit).<= /span>
You should ask yourself if:
If the manual and automated variants are semantically equal and yo= u don=E2=80=99t need to track automation and manual test results independen= tly, you can reuse the same Test issues.
In this case, and since the =E2=80=9Cmanual=E2=80=9D Test would be= already pre-created, from the automation standpoint, you would need to use= a format that provides the ability to report against an existing Test issu= e, given its issue key. For that, you can either use TestNG, NUnit or Robot= framework XML reports. You can also use Xray JSON format, which is unique = that allows you to report the status for each step, while the other ones ca= n=E2=80=99t (they will either PASS or FAIL the whole Test Run).
Examples:
Note: The current Junit implementation (as of 2019), does= not allow you to put labels on the Tests; thus, there is no way to enfo= rce that a given automated test method is mapped against an existing Te= st in Xray.
If manual and automated variant are semantically different or if y= ou wish to track automation and manual test results independently, you need= to have different Test issues.
This will give you some added benefits:
Xray does not enforce a specific way for relating the manual and a= utomated test variant. However, you can, for example, create a link (using = whatever issue link you want, such as "automates") between these Test issue= s.
In this scenario, you would:
At any moment in time, you could deprecate the manual scripted tes= t