Test Cases for Windows Applications

[Pages:32]Test Cases for Windows Applications

Windows 10 Universal Windows Platform ? Desktop and Mobile device families Windows 8.1 Windows and Windows Phone April 2016

Contents

Introduction ........................................................................................................................................................................ 3 1. Launch-related Test Cases ......................................................................................................................................... 3

1.1 Low spec devices .................................................................................................................................................... 3 1.2 Launch on all required device families.............................................................................................................4 1.3 Multi-regional launch............................................................................................................................................4 1.4 Offline launch .......................................................................................................................................................... 5 1.5 Launch time ............................................................................................................................................................. 5 2. Log In Test Cases..........................................................................................................................................................5 2.1 Offline log in ............................................................................................................................................................ 6 2.2 Invalid credentials .................................................................................................................................................. 6 2.3 All log in methods are functional......................................................................................................................6 2.4 Switching away after logging in ........................................................................................................................ 7 2.5 Account creation ................................................................................................................................................... 7 2.6 Account switching ................................................................................................................................................. 7 3. Application Use Test Cases........................................................................................................................................8 3.1 App Switching ......................................................................................................................................................... 8 3.2 Software Input Pad implementation ................................................................................................................ 9 3.3 Touch targets..........................................................................................................................................................9 3.4 Visual feedback ...................................................................................................................................................... 9 3.5 Gestures ................................................................................................................................................................. 10 3.6 Secondary tiles ...................................................................................................................................................... 11 3.7 Command bar with contextual commands................................................................................................... 11 3.8 Application is stable ............................................................................................................................................ 12 3.9 Application performance is responsive ......................................................................................................... 12

3.10 Toast notifications are actionable ................................................................................................................. 13 3.11 Offline mid-use scenarios................................................................................................................................. 13 3.12 Saved status preservation................................................................................................................................ 14 3.13 Portrait and landscape mode scenarios ...................................................................................................... 14 3.14 Core scenarios completed within the application .................................................................................... 15 3.15 In-App purchases............................................................................................................................................... 15 3.16 Geofencing .......................................................................................................................................................... 16 3.17 Cross-Platform adaptive layout ..................................................................................................................... 16 3.18 Application is feature complete ..................................................................................................................... 17 3.19 App Resume........................................................................................................................................................ 17 3.20 Readability........................................................................................................................................................... 18 3.21 Placeholder text and imagery ........................................................................................................................ 18 3.22 Application specific hardware........................................................................................................................ 19 3.23 Cortana ................................................................................................................................................................ 19 3.24 Resuming after idling .......................................................................................................................................20 4. Phone-Only Test Cases ............................................................................................................................................20 4.1 Application resumes successfully from tombstoned state .......................................................................20 4.2 Back button for mobile ...................................................................................................................................... 21 4.3 Continuum for mobile........................................................................................................................................ 21 5. Windows-Only Test Cases .......................................................................................................................................22 5.1 Split and windowed views and display resolutions.....................................................................................22 5.2 Application resumes from a suspended state.............................................................................................23 5.3 Back button for desktop ....................................................................................................................................24 5.4 Desktop and tablet mode switching ..............................................................................................................24 5.5 Multiple input methods .....................................................................................................................................25 5.6 Forward and backward navigation.................................................................................................................25 6. Social Networking Integration Test Cases ...........................................................................................................26 6.1 Shared content .....................................................................................................................................................26 6.2 Share targets.........................................................................................................................................................26 7. Game Specific Test Cases.........................................................................................................................................27 7.1 Game leaderboard...............................................................................................................................................27

7.2 Game achievements and scores .....................................................................................................................27 7.3 Game multiplayer support ................................................................................................................................28 7.4 Roaming Game Saves ........................................................................................................................................28 8. Media Specific Test Cases ........................................................................................................................................29 8.1 Background audio playback..............................................................................................................................29 8.2 Background audio controls ..............................................................................................................................29 8.3 Video pauses playback when the application is in the background .....................................................29 9. ..........................................................................................................................................................................................30 10. WACK Test Findings.................................................................................................................................................30 11. Competitive Parity Test Cases................................................................................................................................30 11.1 Feature parity ? Competitive platforms ........................................................................................................30 11.2 Feature parity - Website ................................................................................................................................... 31 11.3 Performance parity............................................................................................................................................. 31

Introduction

Application functionality is the foundation of user satisfaction. The tests included here are designed to test the most fundamental functional scenarios in Universal Windows Platform (Mobile and Desktop device families) Store applications and games. These tests make no assumptions regarding an application's user interface and verify that an application's behavior is consistent with user expectations and the Windows design guidelines. The reader is encouraged to incorporate these test cases into their software development projects to help ensure high user satisfaction ? and high user ratings.

1. Launch-related Test Cases

1.1 Low spec devices

The application should install and function properly on low spec devices. Expected result: The application should function properly on low spec devices. Note: A `Low spec' phone is defined as a 512MB Windows Phone 8.1 device, ex: Lumia 520, and/or a 1GB Windows 10 Mobile device, ex: Lumia 535.

1.2 Launch on all required device families

The application should install and launch properly on all device families the app is designed to run on.

With Windows 10 developers can write a single application that can be installed across a variety of device families including Mobile, Desktop, and XBOX. By default, Windows 10 applications target all device families. In the application manifest, this is called out as the `Universal' Target Device Family. Such applications will be tested against all device form factors where this application may be deployed. Alternatively, developers can limit the device families for which an application can be deployed. For example, if `Desktop' is specified as the Target Device Family, that application can only be installed on PC devices. When published, this application will only be available in the Store running on PCs ? it will not be available in the Phone store.

Steps to Reproduce:

1. Check the supported device families in the application's manifest. 2. Attempt to install and launch the application on all required device families.

Expected result:

The manifest entry should be restricted only to supported devices when only one device is supported.

More information:

For more information see DeviceTargetFamily.

Target Device Family

Hardware

Desktop

PCs and Tablets running Desktop OS SKU.

Mobile

Phone and Tablets running Mobile OS SKU.

Team

Surface Hub running Team OS SKU.

Universal

All

1.3 Multi-regional launch

The application should launch properly on devices where the local username contains Unicode characters.

Steps to Reproduce:

1. Launch the application on a device where the user local folder path has Unicode characters, ex: c:\users\\.

Expected result: The application launches properly on devices where the local username contains Unicode characters.

1.4 Offline launch

The application should be stable and not crash or close unexpectedly if the device is offline. When the application is offline, the application should warn the user for any requested action that cannot be completed. Steps to Reproduce:

1. Turn airplane mode on and wait 10 seconds. 2. Launch the application. 3. Perform an action that will cause a connection to be attempted. Expected result: The application will detect that the network is not available and alert the user. Application should not crash and provide a relevant error message to user. Application should

not display the exception stack to the user. The application can also implement an offline (cached) mode without alerting the user.

1.5 Launch time

The application should launch in a reasonable amount of time, and should display a loading or progress indicator if the application takes a while to load. Steps to Reproduce:

1. Launch the application. 2. Record the start-up time. Expected result: The application displays a loading or progress indicator if the application takes a while to load,

and the content loads in a reasonable amount of time.

2. Log In Test Cases

The following test cases apply only to applications that support log in.

2.1 Offline log in

When the application is offline and the user attempts to log in, the application should warn the user of the offline status.

Steps to Reproduce:

1. Turn airplane mode on and wait 10 seconds. 2. Launch the application. 3. Attempt to log in with valid credentials. 4. Verify that an appropriate error message appears. 5. Turn airplane mode off and wait 10 seconds. 6. Return to the application. 7. Log in with valid credentials. Expected result:

When attempting to log in without a network connection, an appropriate error message should appear warning the user of the offline state.

When the network connection has been resumed, log in should work appropriately.

2.2 Invalid credentials

The application should warn the user appropriately when invalid credentials are entered.

Steps to Reproduce:

1. Launch the application. 2. Attempt to log in with invalid credentials. 3. Verify that an appropriate error message appears. 4. Log in with valid credentials, changing the casing in the username field. Expected result:

When attempting to log in with invalid credentials, an appropriate error message should appear warning the user that the credentials are invalid.

The username field should not be case-sensitive. When correct credentials are entered after a failed attempt, log in should work appropriately.

2.3 All log in methods are functional

All available log in options should be fully functional and appropriately implemented.

Steps to Reproduce:

1. Launch the application. 2. Log in using all available options with valid credentials. Expected result: Application logs in when valid credentials are entered. Social networking log in and/or sign up is processed using the services' login page(s) and not

using application pages for this purpose.

2.4 Switching away after logging in

The application should load content successfully after switching away during the loading process. Steps to Reproduce:

1. Launch the application. 2. Log in with valid credentials. 3. While the application is loading, switch away from the application. 4. Wait one second and return to the application. Expected result: Content should load successfully after returning to the application.

2.5 Account creation

The creation of accounts within the application (when available) should function properly. Steps to Reproduce:

1. Launch the application. 2. Create an account if the option is available, entering valid information when prompted. 3. Exit the application. 4. Attempt to log in with the newly created account. Expected result: Accounts can be successfully created within the application when the option is available. If an email verification is required, the application should state this and the verification email

should arrive within an hour of creating the account. Username, email, and password requirements are made clear to the user.

2.6 Account switching

Users should be able to log into various accounts properly when the option is available. Steps to Reproduce:

1. Launch the application and log into account #1. 2. Navigate through the application, saving information to the account whenever possible. 3. Log out and exit the application. 4. Launch the application and log into account #2. 5. Navigate through the application. Expected result: Logging into a second account should function properly after logging out of a first account. Data from a first account should not appear when logged into a second account.

3. Application Use Test Cases

3.1 App Switching

When switching away from the application, network requests are cancelled. The application should detect this situation and re-issue network requests when application is reactivated. Steps to Reproduce:

3. Launch application. 4. Navigate through the application. 5. During loading (when loading indicator is present), switch away from the application. 6. Wait one second and return to the application. Expected result: Functionality completes successfully and data is downloaded without error or exception. More information: For more information on Fast App Switching in Windows Phone applications, see Get Ready for Fast Application Switching in Windows Phone and App activation and deactivation for Windows Phone 8 For Windows applications, see Managing app lifecycle so your apps feel "always alive"

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download