You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Xray's roadmap is constantly reviewed and redefined. We update often, depending on feedback we receive from our clients and internal stakeholders.

Our release plan is available in our Jira issue tracker, although account registration is required. Feel free to vote in the issues that you would like to see implemented.

Here you can find a list of features that define our main goals for future releases. This doesn't mean that other potentially smaller features won't be implemented as well.

Future versions

  • Revamp Manual Steps UI

    A wider, more usable UI that provides the ability to edit all step-related fields at once, in a column or row-based layout.

  • Test Step fields

    Custom step fields for test cases, that can complement the standard ones (Action/Step, Data, Expected Result).

  • Test Run fields

    Custom fields for test runs, that can be used to store additional, structured information in test runs.
  • Updated Add-ons for Bamboo and Jenkins

  • Call Test

    Quick overview

    Ability to call an existing test from a step of another test and thus use tests as reusable building blocks for the composition of more complex testing scenarios.

    In this scenario, the called test can be executed independently or be used as a step of a broader test (e.g. "login as the admin user").

  • Test Parameterization

    Quick overview

    Ability to define variables in the test specification (e.g. the steps) that can be replaced by values inherited from the calling test, for example. In that scenario, the called test is used as a parameterized template (e.g. "login as the specified user").

    The test will be executed once unless data-driven testing is performed; note that data-driven testing will be implemented using the foundations of test parameterization.

  • Data-driven testing

    Quick overview

    Ability to perform data-driven testing (i.e. execute the same test against multiple times, for different combinations of data).

    Data may be defined at the test level of the caller test, or directly in the test itself, for example.

  • Dynamic Test Plans

    Quick overview

    Besides a more controlled approach for planning the testing effort (i.e. where testers clearly and explicitly add the tests to the Test Plan), we aim to provide dynamic and flexible approach: Test Plans that contain a dynamic list of tests, based on user-defined criteria. 

  • Test Natures

    Quick overview

    Allow the same Test entity to have different natures (e.g. both "manual" and "automated"), avoiding the need to duplicate tests due to their nature.

    This way, a Test may contain both results for manual scripted testing and the Cucumber variant.

  • Custom Test Types

    Quick overview

    Ability to provide management for test types and thus provide additional, user-defined test types besides the standard ones (i.e. Manual, Cucumber, Generic) 

  • Cross-project reports
  • Time Tracking
    • Calculated Time Estimates
    • Track Execution Time
  • Manual Step Library
  • Project Settings
  • (...) 




  • No labels