Page History
Info |
---|
This article aims to explain some Xray Anti-patterns patterns that can lead to future constrains or even data integrity issues. Please use this information carefully and taking in consideration your own setup and team processes. |
UI Expand | ||
---|---|---|
| ||
|
Anti-Pattern
Description:This anti-pattern is about creating/having manual, script-based Test cases, without Test Steps.
Manual Tests Manual tests should have clearly defined stepsSteps. If a user is not creating stepsSteps, it may indicate that they are using the wrong test Test type and will lead to other testers misinterpretation of what needs to be done. Allowing this anti-pattern to spread will lead to significant issues such as:
- Inconsistent Test Executions,.
- Difficulty in reproducing Defects, and ultimately Reduced ultimately, reduced Test Coverage, since critical actions might have been missed or executed incorrectly.
Solution
:The solution for this anti-pattern goes with user educationinternal coaching, clearly defined parameters & and standards for test Test case documentation, recurrent audit, and also automating repetitive tasks where detailed steps Steps are critical. Manual, script/structured Test cases should have a number of Steps that explain the intent and the expected goals; we should also avoid adding too much detail into it, as it creates unnecessary bureaucracy and makes our est specification more dependent on the implementation and thus more fragile.
However it may also be the case we are using a wrong Test type, in that case we suggest revisintg revisiting the following articles for Generic/Unstructured Test Type.
DC: https://docs.getxray.app/pages/viewpage.action?pageId=62268044
Cloud: https://docs.getxray.app/display/XRAYCLOUD/UnstructuredAudit and Review
We suggest a recurrent audit; you can define its cadence, especially in Team Meetings team meetings or Dailies dailies to assist and provide feedback on the spot.
Should you be using Xray Data Center, feel free to use the below JQL as a Saved filter with a Filter Result kind of gadget in a dashboard:
Code Block |
---|
issue in manualTestsWithoutSteps() |
or
Code Block |
---|
issue in manualTestsWithoutSteps("saved_filter") |
Should It should look like this:
Filter Results Gadget (Figure 1)using the following Saved Filter: "issue in manualTestsWithoutSteps() AND Project = "Your Project Name""
Should you use Xray Cloud, it is on the verge of receiving a sort of insights tool which will give you notice of this anti-pattern and others in a Xray page.
Figure 1 - Filter
Xray Cloud users can currently obtain information about this anti-patternusing the Xray Document Generator.
Snippet code:
Code Block |
---|
&{for issues}
#{if (%{'${IssueTypeName}'.equals('Test')})}
#{if (%{'${TestStepsCount}'.equals('0')})}
${Key} - ${Summary}
#{end}
#{end}
&{end} |
Learn More
One key feature you can make use of is Modular Tests in which previously defined manual tests Manual Tests with respective steps Steps can assist you to easily compose a Test Scenarioscenario.DC: https://docs.getxray.app/display/XRAY/
+Xray Academy
Cloud: https://docs.getxray.app/display/XRAYCLOUD/Modular+Tests
Join for free our Xray Academy and take theThe Xray Academy offers Xray Essentials for Cloud & Xray Essentials for Data Center Course to help you get familiarized with how to use the Modular Test Functionalityfunctionality.
Figure 2 - Xray Academy
We In fact we encourage your team to go through all the courses → Xray Academy Xray Academy courses.
Expand | ||
---|---|---|
| ||
If you have questions or technical issues, please contact the Support team via the Customer Portal (Jira service management) or send us a message using the in-app chat. |