Page History
...
In sum, an exploratory test in Xray will be a Test. A testing session, that represents the testing performed for a given charter, will be abstracted as a Test Run for the exploratory Test.
Exploratory Testing (ET) concept | Xray concept |
|---|---|
Test / Test charter | Test
|
Session | Test Run |
| Info | ||
|---|---|---|
| ||
|
...
Performing the test session (i.e., "executing" the test)
To perform Before performing our test session, we start it by scheduling need to schedule an execution for our Test. The way to do this in Xray, is to schedule a Test Execution for our Test (or to include our Test in an existing Test Execution).
Test Executions can be created from multiple places (e.g., from Test Repository, Test Plan, etc), including directly from the Test issue screen.
| Info | ||
|---|---|---|
| ||
If you have multiple testers involved in your exploratory session, then you can create different Test Executions each one assigned to a different tester; you may use the Test Execution planning dates to define the fixed time-frame allocated to your session. The Test Execution description can be used to specify the tester charter, which complements and focuses the session charter for the tester(s) involved in that Test Execution. Please note that a Test Execution can only contain the same Test onc |
During the test session, on the Test Run execution screen, we can:
- report the overall status of our testing session, using the Execution Status field. For example, as PASS if all seems good enough, or as FAIL if there are major issues; you can also use custom test run statuses if you want
- leave notes, using Comment section. As it supports wiki markup, we can use it to organize our text notes; even though there's no structure, we recommend having a brief summary and having the text notes organized by categories
- report defects, on the Execution Defects section
- attach evidence, on the Execution Evidence section. We can attach logs, or other files that may be relevant, including screenshots; we can use our tool of choice for taking screenshots. You can use copy&paste; whenever "pasting" an image the following dialog will appear
Using Xray together with Xray Exploratory App
The Xray Exploratory App (XEA) is a side companion desktop app that is used to assist testers on exploratory testing related tasks.
| Info | ||
|---|---|---|
| ||
|
Concerning the integration with Xray, there are two main flows to have in mind:
- define the test charter in Xray, by creating an exploratory Test, and then use XEA to assist on note-taking and report results back to Jira, where the team can analyze them and track its impacts
- use XEA to define the test charter, assist on note and evidence taking during testing, and then report results back to Jira, where the team can analyze them and track its impacts
The subtle difference is which tool we'll use to create/define the exploratory Tests. Teams may use the first approach, where Xray is the master, if they wish to follow similar processes as they do for manual scripted test cases, and have some sort of management/planning.