Page History
...
Teams use it during the early stages of the testing process, including when they create scenario-based requirementsRequirements. Benefiting from the model-based approach and the intelligent augmentation algorithm, Xray Test Case Designer's Test suites have repeatedly proven to find more defects - and do so more efficiently - than hand-selected Test suites.
Xray Test Case Designer carefully constructs combinations of test Test conditions to achieve maximum coverage with the fewest possible testsTests, using statistics-based optimization methods refined over more than 40 years.
...
With Xray Test Case Designer, the goal is to enhance both the speed and the quality - teams create more thorough tests Tests faster, find defects earlier in the process, and do so in fewer tests Tests to run and maintain over time, which leads to cost savings.
...
Each time you generate a set of scenariosScenarios, the Xray Test Case Designer automatically creates insightful interaction coverage reports, clearly showing what is and isn't covered by any chosen scenario. These visualizations facilitate clear and efficient communication among stakeholders.
With Xray Test Case Designer's coverage graphs, you'll have clear, actionable, and fact-based answers to questions like "How many tests Tests are enough?".
Automating Faster
...
- Rapidly create clear, consistent Test Steps that leverage Behavior Driven Development principles. The primary benefit is the one-to-many relationship between Xray Test Case Designer scripts Scripts and the data scenariosScenarios.
- Export one scenario block into multiple skeletal scripts Scripts based on your chosen language (using "the Automated Test Framework" option).
- Maintain and reuse script Script components faster, thanks to the model-based approach.
...
The most common type of wasteful repetition occurs when certain system paths and Test input combinations are tested repeatedly across multiple tests Tests (instead of branching out). Based on our analysis of thousands of hand-selected Test suites, even those achieving "requirements Requirements coverage" often fail to thoroughly Test critical system interactions.
...
A Test Model is an abstraction of a focused use case you aim to Test. This model is built around a specific scope (e.g., "book a flight") that can be exercised in different ways, depending on a combination of input parameters (e.g., "origin, destination, number of seats, date"). To find bugs related to the input parameters and increase coverage, an optimized set of test Test cases (manual or automated) can be derived from it.
...
Parameters define the variables and their possible values within the Test Model. Typically, these refer to input variables. Parameters, along with restrictions specified using Rules, are used to derive the combination of parameterParameters/valuesValues.
| Info |
|---|
Test parameterization is a powerful practice that allows the same test to be executed multiple times with different parameters. Parameters are similar to input values (variables) that can change with each execution. |
...
Conversely, Rules can also enforce scenarios Scenarios where certain lengthy parameter value combinations must be incorporated into the test Test suite as a priority.
Scenarios
Scenarios are are the generated combinations of input parameter values, where each row represents a combination of parameters Parameters (and their valuesValues) to be used in a Test.
Think of Scenarios as an optimized dataset used to iterate your Test Model multiple times, testing it under slightly different circumstances.
Not all parameterParameter/value Value combinations are created. Xray Test Case Designer uses coverage optimization algorithms (e.g., pairwise, n-wise) to achieve high coverage with few Tests. This can be adjusted for greater coverage if needed.
...
Scripts contain detailed Steps with actions and expectations for your test scenarios. Scripts can be manual or automated.
For manual Test scriptsScripts, detailed Steps and expected results can be specified, with parameters mentioned. These parameters will be replaced by the respective values when exporting the Tests later.
For automated Test scriptsScripts, you can specify Gherkin (e.g., Cucumber) Scenarios or Scenario Outlines, or even Robot Framework Test cases. Similar to manual Test scriptsScripts, parameters can be mentioned in the specification and replaced by proper values later.
Features
| Features | Supported? |
|---|---|
| Create, view, edit, and copy Test Models |  |
| Test Model revision history |
|
| Import Test Models from Excel |
|
| Import Test Models from mind maps (OPML) |
|
| Share Test Models |
|
| Export Test Models |
|
| Parameters | |
| Create, view, and edit Parameters |
|
| Order Parameters |
|
| Add Value Expansions (equivalence classes) |
|
| Bulk update |
|
| Boundary/ranged values |
|
| Rules | |
| Constraints definition |
|
| Invalid, Bound, Skip constraints |
|
| Complex multi-parameter rules |
|
| Forced Interactions definition |
|
| Import Forced Interactions |
|
| Scenarios | |
| Standard and optimized |
| Scenarios generation |
|
| Pairwise and N-way interactions |
|
| Mixed-strength interactions |
|
| Scenario Freeze option |
|
| Export Scenarios |
|
| Scripts | |
| Manual Tests |
|
| Native support for BDD (Gherkin/Cucumber) |
|
| Analysis | |
| Coverage Matrix |
|
| Coverage Graph |
|
| Review | |
| Notes |
|
| Mind Map View |
|
| Scorecard |
|
| Info |
|---|
...