Session Based Test – Analysis Session

The Analysis Session is the forth out of 6 types of session reports you can create when you use the Session Based Test approach. This report follows the Setup Session report. The goal of the analyses sessions is to “get ideas for deep coverage”. We will do a risk assessment to guide further testing. We will brainstorm about test ideas related to the application, identify the primary functions of the application. If needed, we construct a test coverage outline.

Most of the time I’ll make a single session report per user story. I put in here a copy of the information from the user story. This information includes description likes ‘Definition of Done’ or ‘Acceptance Criteria’. I have the information when I have to work off line. I can add test ideas to the file which are releated to the user story.

One extra, separate Analysis Session report, is the list with risks. I make this because most of the times the user stories are part of a sprint and belong to the same epic. Here I mentioned the risks which I will assess during my deep coverage tests. Risks mentioned here are related to the new or changed features of the application and the regression issues caused by these features.

Below an other example of a Analysis Session report. It is the information of a user story an assessment how to approach the test of some waiting time screens

CHARTER
———————————————–
AAMBR-1783 : Average waiting time indicator

#AREAS
EPIC | CallCustomerServices – MBAA-1780
Session | Analysis session

START
———————————————–
02/09/16 10:00am

TESTER
———————————————–
Peter Schrijver

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

#DURATION
short

#SESSION SETUP
0

#TEST DESIGN AND EXECUTION
100

#BUG INVESTIGATION AND REPORTING
0

#CHARTER VS. OPPORTUNITY
100/0

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

TEST NOTES
———————————————–
As a user
I want to see an indication of the waiting time, before calling Customer Services, in order to decide whether I will call now or at a different time.

Acceptance criteria
• The customer will be informed on the average waiting time, in text, retrieved from Tridion.
• The average waiting time will be a single selection out of the following 4 options

Key Description
IVR_WAITINGTIME_TEXT_STATUS0 Waiting time unavailable
IVR_WAITINGTIME_TEXT_STATUS1 Waiting time less than 1 minute
IVR_WAITINGTIME_TEXT_STATUS2 Waiting time less than 5 minutes
IVR_WAITINGTIME_TEXT_STATUS3 Waiting time more than 5 minutes

• The waiting time information is displayed in the same view as the call button.
• The waiting time indicator is only shown when the customer is identified and the selected topic has a number supported by Genesys (ACS)

Error scenario’s
When service (BAPI4962 – GetStatistics) is not available;
• The customer is informed that the waiting time indicator is not available (STATUS0).
• Only static information on waiting time is displayed.
• The bank mail button will not be displayed, as we can not derive this from the
waiting time.

BUGS
———————————————–
#N/A

ISSUES
———————————————–
#N/A

Below an other example of a Analysis Session report. It is an assesment how to approach the test of some waiting time screens

CHARTER
———————————————–
Test ideas for displaying waiting messages

#AREAS
EPIC | CallCustomerServices – MBAA-1780
Session | Analysis session

START
———————————————–
02/09/16 2:30pm

TESTER
———————————————–
Peter Schrijver

TASK BREAKDOWN
———————————————–
#DURATION
normal

#SESSION SETUP
0

#TEST DESIGN AND EXECUTION
100

#BUG INVESTIGATION AND REPORTING
0

#CHARTER VS. OPPORTUNITY
100/0

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

TEST NOTES
———————————————–
We have no control over the message we get back from the Genesys back-end. To make sure we see all screens we have to intercept the response of the request for statistics

Below a response message from the backend

{
“statistics”:
[{
“statistic”
{
“context”: “MORTGAGES”,
“channel”: “PHONE_INBOUND”,
“waitingTimeLongestWaitingCustomer”: 0,
“numberCustomersWaiting”: 0,
“averageWaitingTime”: 0
}
}]
}

With the use of a tool, i.e. ‘CharlesProxy’, we set a breakpoint on the message and try to alter the response message

The message to be intercepted is:
GET https://www-thebank.nl/custcareservices/statistics?channels=PHONE_INBOUND&contexts=MORTGAGES

For this example you are setting a breakpoint on ‘MORTGAGES’. In document ‘REST Service Contract Specification.docx’ You can find a list of all contexts and channels.

“averageWaitingTime” is the variable that determines which screen is displayed

between 0 and 60, you will see on screen ‘Waiting time less than 1 minute’
between 60.01 and 300, you will see on screen ‘Waiting time less than 5 minutes’
above 300.01 you will see on screen ‘Waiting time more than 5 minutes’

When there is no “averageWaitingTime” given you will see on screen ‘Waiting time
unavailable’

BUGS
———————————————–
#N/A

ISSUES
———————————————–
#N/A

Advertisements

One Comment 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