Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
indextrue
titleDescription

A test session is a document that tracks the exploratory test defined by a test charter. Add all sort of information. This document is like a journal for the timeboxed journey that discovers qualities of the software product.

On creation of the test session document you typically do not need to add any information to the wizard. Just click 'Create'! If you change your mind, you may rename the document or edit the short description later.

Note that this document delegates per default to the parent document, which should be a test charter.

Section
titleProperties
Transclusion
documentNote Box referencing common Document Properties
idsBox

Section
titleSponsors

Specify a list of stakeholders that are interested in the outcome of the exploratory test and therefore sponsor it.

This information is typically synchronized with that of the associated test charter.

Section
titleExperts

List the names of stakeholders who may provide additional information on the area being examined.

This information is typically synchronized with that of the associated test charter.

Section
titleTimebox

Define the timebox within to run the session.

Section
titleActor

Reference a user character the tester runs the tests. This may reference persona to inspire the finding of the opportunities on where and how to explore the software.

Section
titleSections
Section
titleDescription

Document the purpose of this test session.

Section
titleSummary

Write a short summary about the test result intended for other testers. A summary for the sponsors will be given in the test reports.

Section
titleCharter

Simply transclude the content from the associated test charter. Per default the transclusion is defined by the delegate document of the Document Properties Marker Macro that is set the parent document this session document has been created for.

Section
titlePreparation

List things to do before starting the exploration session. This is especially useful to plan the journey in advance. If the team is ready to go, but has no test data or access to some required systems, this could be quite uninspiring.

Section
titleExploration

This section will compile all information found on the journey. Either add the discoveries as separate child documents or write it directly to the sections (removing the use of the Display Table Macros).

Section
titleLog

Log whatever seems interesting, either for this session or for additional sessions that will be based with their own charters.

Logs are typically Step documents. You may add many resources to these documents and only transclude the refined information.

Section
titleTest Ideas

You may stumble upon interesting information that call for further tests. But to not overrun your timebox you want to add these ideas as new charter documents to investigate them later.

Section
titleQuestions

Everything you cannot answer by yourself or by an expert you know of. The answer has to be found elsewhere later.

The doctype for questions is Open Issue. It is part of the project management add-on, available as open source on Bitbucket.

Section
titleRisks

If you encounter risks you need to tackle later, write them down here.

The doctype for risks is Risk. It is part of the project management add-on, available as open source on Bitbucket.

Section
titleSurprises

Anything special you do not want to be only part of the log section.

Section
titleSubordinate Test Sessions

In case you want to divide the session into smaller sessions, possibly conducted by different groups.

Section
titleIssues

A list of issues you created with JIRA as part of your discoveries.

You may need to adjust the query to match the tickets you created.

Transclusion
documentDocument Sections
idsstandard-sections-bottom

...