Session Based Test – Layout session report

CHARTER
———————————————–
A charter summarizes the goal or activity of the session. It is  a “clear mission for the session”. You can define a charter before you start your session. It is a statement of how the session will be focused. During your test execution, you gather information based on the observation you make. You can come to the conclusion that you have to alter the charter. So the charter after the session can be changed, if necessary, to reasonably characterize the actual focus of the session.
Something else can be state here which is more based on test ideas you have created or test cases you have predefined which (can) have a test case ID.

Examples:
Test Defect ATP-HLR-IL-SOAP-030 : HLR – IL SOAP request : getBasicServiceList, invalid values
……

#AREAS
Areas can be:

  • Version of OS
  • Version of SW
  • Applications used
  • Project specific areas
  • Session specific information

Note : It is useful to write it down like below

Browser | Google Chrome | Version 35.0.1916.114
Release | HLR | 1.2.0 – 20140606
System | HLR
System | SPR
System | IL
Tool | SOAP UI | Version 5.0.0
Environment | PET

In this format, it can be used to process the report by some of the tools that are available

START
———————————————–
Date and time of test session start up.
Use notation yy/dd/mm hh:mm am/pm
Example : 14/15/06 12:14pm

TESTER
———————————————–
Name of tester. This can be more than one person.

TASK BREAKDOWN
———————————————–

#DURATION
A predefined amount of time that should be spent on the current test session.
Different values :

  • “Short” (60min),
  • “Normal” (90min),
  • “Long” (120 min).

After a completed test session the tester fills in the most suitable value of duration (or tool will provide this). You are free to determine your own standard which serves you better. As an example you can do the following:

  • “Short” (< 1 hour),
  • “Normal” (between 1 and 2 hours),
  • “Long” (between 2 and 4 hours),
  • “Double Long” (between 4 and 8 hours).

You even can give story points to this:

  • “Short” (1 point),
  • “Normal” (2 points),
  • “Long” (3 points),
  • “Double Long” (5 points)

#SESSION SETUP
Time required in setting up the application under test. (Integer between 0 – 100, [S])

#TEST DESIGN AND EXECUTION
Time required scanning the product and test. (Integer between 0 – 100, [T])

#BUG INVESTIGATION AND REPORTING
Time required finding the bugs and reporting to the concerned. (Integer between 0 – 100, [B])

Note: [S] + [T] + [B] = 100

#CHARTER VS. OPPORTUNITY
Time spent “on charter” and “on opportunity”. (Ratio of session duration )
Opportunity testing is any testing that doesn’t fit the charter of the session. The tester is not restricted to his charter, and hence allowed to deviate from the goal specified if there is any scope of finding an error

DATA FILES
———————————————–
Data files can be :
Screenshots
Word doc file with test notes
Log files
(Part of) Requirements
Test data
Is reference material for future occasions (regression test)
Collect all files into a zip file. This file is to be stored on a predefined location. Advice; name the file using the filename of the session report.
If the name is ‘et-psc-140615-a.ses’, name the zipped data file ‘et-psc-140615-a.ses.zip’ or ‘et-psc-140615-a.zip’.
It is easy to find when you need it later.

TEST NOTES
———————————————–
The tester(s) write down anything of importance about the test session that e.g. shows how the included tests were performed, how the test approach developed during the session and what challenges that needed to be solved or that was at least noted. The format for the test notes is decided by the tester, anything goes.
Notes can be taken during the session or afterwards. It also can be a collection of screen shots with supporting text/remarks or even a reference to a video recording.

The test notes can also be used to inform the next tester with information of part of the the charter that should be explored further or it can also be used the person who use this session report for test automation purposes

I use the test note section to describe one or more test which a part of the charter.
I give each test a simple ID like ’Test 1:’ and a brief description of what the test contains. An example can be: Test 1: Execute a getBasicServiceList request via IL, using invalid subscriberId
For each test I give a test result, which can be PASSED, FAILED or HOLD. By working via this process, I also create for myself a test summary

BUGS
———————————————–
Place to report bugs found during the session.
Input for formal bug tracking system, like QC.
The most common way is to just add the ID number (i.e QC43718) and title (optional) for the reported bug from the defect management system that is used at the current company.

Note : “A bug is anything that threatens the value of the product.”

ISSUES
———————————————–
Place to report issues found / came up during the session. E.g. if the test environment caused problems or if a problem was found that needs more exploration to it. Is it a bug or not?
Need follow up investigation.
Can be input/idea for a new or follow up session

Note “An issue is anything that threatens the value of the testing, or of the project, or of the business.” 
Issues that affect testing make it slower and harder. Issues give bugs more opportunity and more time to hide, so fixing issues might sometimes be more important than fixing bugs.

To get more information about Session Reports, see the website of James Bach, Michael Bolton and Paul Carvalho

==================== Sample Session Test Report ====================

CHARTER
———————————————–

#AREAS

START
———————————————–

TESTER
———————————————–

TASK BREAKDOWN
———————————————–
#SESSION SETUP

#TEST DESIGN AND EXECUTION

#BUG INVESTIGATION AND REPORTING

#CHARTER VS. OPPORTUNITY

DATA FILES
———————————————–

TEST NOTES
———————————————–

BUGS
———————————————–

ISSUES
———————————————–

Advertisements

2 Comments Add yours

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s