SE401:Group32:Tool Scenarios
Concrete Scenarios
Mobile Phones/PDA elements of applications – Functional testing
- Textfields
- Labels
- Textareas
- Images
- Tables
- Video content
- Buttons
- Scrollbars
Mobile Phones/PDA elements of applications – Environment testing
- Response times
- Memory usage
- Network availability
- Power consumption
Mobile Phones/PDA elements of applications – Aesthetics testing
- Aesthetics
Scenario 1 - TextFields
Platform: mobile phone or PDA
Element: Textfields
Input: User inputs text into a textfield that stretches longer than the visual space available on the screen of the mobile phone.
Expected outcome: The textfield still encompasses the entire string but shows the most recent characters inputted into the textfield i.e. the cursor moves with the text displaying the most recently inputted characters
Scenario 2 - Labels
Platform: mobile phone or PDA
Element: Labels
Input: Label that is longer than the visual screen width is created.
Expected outcome: Horizontal scrollbars should be able to be used to change the view to see the rest of the label
Scenario 3 - Textareas
Platform: mobile phone or PDA
Element: Textareas
Input: User inputs text into a textarea that is half the height of the screen. The text is longer than the space available of the text area on the screen of the device.
Expected outcome: The textarea still encompasses the entire string but once the space is taken up the text area scrollbars should then be visible for the user to scroll up and down. Note: this is not the actual screen scrollbars
Scenario 4 - Images
Platform: mobile phone or PDA
Element: Images
Input: An image is larger than the screen.
Expected outcome: Horizontal and vertical scrollbars should be able to be used to change the view to see the rest of the image
Scenario 5 - Tables
Platform: mobile phone or PDA
Element: Tables
Input: There is a table that contains more columns than can be shown on the screen
Expected outcome: Horizontal and vertical scrollbars should be able to be used to change the view to see the rest of the table
Scenario 6 - Video Content
Platform: mobile phone or PDA
Element: Video content
Input: A video is loaded in the application and user presses play
Expected outcome: There should be minimal lag and the video should play relatively smoothly
Scenario 7 - Buttons
Platform: mobile phone or PDA
Element: Buttons
Input: User clicks the exit button of the application
Expected outcome: The button should be highlighted i.e. show that is has been pressed and the application should exit
Revised Scenario 7
CANCEL THIS SCENARIO as it is not feasible
Scenario 8 - Scrollbars
Platform: mobile phone or PDA
Element: Scrollbars
Input: User clicks the arrow keys on the device
Expected outcome: The screen should move up, down, left or right accordingly and dynamically change the position of the scrollbars
Scenario 9 - Response times
Platform: mobile phone or PDA
Element: Response times
Input: User clicks a button that should go to another screen or page of the application
Expected outcome: Appropriate screen or display is displayed almost instantly (less than 1 second)
Platform: mobile phone or PDA
Element: Functional navigation
Input: User clicks a button that should go to another screen or page of the application
Expected outcome: Appropriate screen or display is displayed
Scenario 10 - Resource usage
Platform: mobile phone or PDA
Element: Resource usage
Input: User loads a large image on an application
Expected outcome: This should not incur too much memory overhead
Scenario 11 - Network availability
Platform: mobile phone or PDA
Element: Network availability
Input: Network becomes unavailable
Expected outcome: Application should be switched to an offline mode so the user can still perform some functions. This may involve the use of the cached data on the mobile device.
Scenario 12 - Aethetics: Colours
Platform: mobile phone or PDA
Element: Aesthetics - colours
Expected outcome: Colours should be consistent i.e. contrasting colours for buttons and background etc. Colours should be intuitive for various representations of form elements i.e. a “go” button should be green and not red
Scenario 13 - Aesthetics: Form layout
Platform: mobile phone or PDA
Element: Aesthetics – form layout
Input: On the screen there’s 2 textfields, 2 text labels to identify these textfields and an image
Expected outcome: Image should be centred on the screen. Textfields aligned to the left. Labels should be to the left of these textfields or above them. Also the textfields and labels should aligned with each other
Scenario 14 - Aesthetics: Form layout
Platform: mobile phone or PDA
Element: Aesthetics – form layout
Input: On the screen there’s 2 textfields, 2 text labels to identify these textfields and an image that all span across the visible area of the screen
Expected outcome: Image should be centred on the screen. Textfields aligned to the left. Labels should be to the left of these textfields or above them. Also the textfields and labels should align with each other. Finally scrollbars should become visible in order to be able to navigate the screen and view all the elements.
Scenario 15 - Power Consumption
Platform: mobile phone or PDA
Element: Power consumption
Input: The idle instance of the application is running for a period of 5mins. The status of the mobile battery is recorded or measured. The testing process begins. Once the test scripts have been executed and the phone sends back the raw data back to the PC to be processed, a reading of the new battery energy levels is made.
Expected outcome: The battery power remaining should be no less than 95% of the original reading made prior to testing.
Scenario 16 - Aesthetics - General form layout
Platform: mobile phone or PDA
Element: Aesthetics - General form layout
Input: Given a particular components X (E.g. Label) , Y (E.g. TextField) and Z (E.g. Image) of the form, F, the extraction of the absolute positions of the components (specified in a suitable metric such as Pixels).
Expected outcome: The checking of relative positions of the components based on the intended layout. E.g.: X should be to the left of Y and above Z. Y should be to the right of X and above Z. Z should be below both X and Y.
Scenario 17 - Aesthetics - Image screen space usage
Platform: mobile phone or PDA
Element: Aesthetics - Image screen space usage
Input: Form with an image displayed on the screen.
Expected outcome: For any given mobile device (various screen spaces) the amount of space that the image should take up as a percentage of the maximum screen space should not be greater than 70%.
Scenario 18 - Functional testing - Multihoming capability
Platform: mobile phone or PDA
Element: Connection
Input: The bluetooth connection becomes unavailable
Expected outcome: The connection should be able to identify other possible connection methods such as GPRS, WIFI etc.