Session Based Test – Setup Session

The Setup Session is the third out of 6 types of session reports you can create when you use the Session Based Test approach. This report follows the Survey Session report. The goal of the setup sessions is to “create testing infrastructure”. How we are going test the application? What do we need to realize the test infrastructure we want to use? Who can help us?

Here you need to determine which environment you are going to test with. Most of the time this is covered in a release number. Also you determine which application(s) you are going to test with. Also these contain some kind of release ID.

Specific for Mobile App testing, here you also can determine which OS version you are going to test on for iOS and Android. Also a selection of devices if needed.
If your application is going to be used on a browser, you can mention here which type and version of browsers you are going to test with.

Everything related to your test environment, you have to mention it in this session report. Below an example of a Setup Session report

CHARTER
———————————————–
Setup of In App Signing

EPIC | In App Signing – BR-2193
Session | Setup session

START
———————————————–
03/29/15 4:15pm

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
———————————————–
#N/A

TEST NOTES
———————————————–
The set up of the environment is as follows

Environments
The Acceptance environment used must be on backend release R116. This release contains the back-end solutions for our user stories.
Normally we use Acceptance1 environment, but we probably have to start with Acceptance2 environment.
The App version release version is 8.5. The software of this App version can be downloaded from the buildserver directly on the mobile device. This release contains the front-end solutions for our user stories.
Note that when the App goes live, the release of the backend is R118. Some extra regression tests is needed later on.

Devices
The feature works for both iOS and Android devices. We will test with the most popular devices when available. Otherwise we will make use of simulators/emuators.

Browsers
Due to the fact that we have to use Mobile Web-browser Apps, we have selected the most popular Web-browser Apps for both iOS and Andoid platform
on Android : Firefox, Chrome, Opera and Native
on iOS : Firefox, Chrome, Opera and Safari

OS versions
iOS supported versions, from iOS 7.0.x onwards
Android supported version, from Android 4.0.3 onwards

The device/OS combination selected will be based on popularity/availability.
Other combinations can be used when relevant.
Focus is first on functionality of the App itself. This can used as a reference for other combinations to test.

Configuration
Tridion needs to be configured to support our test effort.

Test approach
Collect some iOS devices and some Android devices on different OS levels. Configure Tridion with entry point information

The user stories MBR-2194, MBR-2226 and MBR-2310 are no subject for automation. These user stories contain actions that need interaction with an responsive web-App.
Further, a mindmap is created where test areas are identified. These are based on the user stories involved

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

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

Advertisements

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