Date: Fri, 29 Mar 2024 13:00:04 +0000 (UTC) Message-ID: <1700104080.11798.1711717204890@docs.getxray.app> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11797_1050429695.1711717204890" ------=_Part_11797_1050429695.1711717204890 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In order to investigate, evaluate and ascertain the completeness= and quality of a project, developers perform quality assurance tests. Test= ing can be performed as individual components/units using Tests, or as a wh= ole using Test Sets. The goal is to check and verify if a specific tar= get requirement is applied, even when determined preconditions are set. It = also helps prevent and uncover situations and defects that could negatively= impact the overall usability of the final product.
A full test specification may be done using just a Test issue, where you specify the steps= and the expected results. Sometimes, you may prefer to abstract the initia= l conditions instead of writing them directly as the first Test steps, enab= ling you to use them in different tests. In this case, you may create one o= r more Precondition issues = and associate them to a Test.
Although tests may be edited anytime, the immutability of tests is guara= nteed whenever tests are scheduled to be executed in some test Execution.= p>