QA/FLAC support: Difference between revisions

Jump to navigation Jump to search
Line 57: Line 57:
<br>'''Full Testing will be performed on:'''
<br>'''Full Testing will be performed on:'''


Windows 7 <br>
'''Windows 7''' <br>
Windows 10 <br>
'''Windows 10''' <br>
Ubuntu 16.04 LTS
'''Ubuntu 16.04 LTS''' <br>
Mac OS X 10.6 or later
'''Mac OS X 10.6''' or later
 
== Test Objectives ==
This section details the progression test objectives that will be covered. Please note that this is at a high level. For large projects, a suite of test cases would be created which would reference directly back to this master.
This could be documented in bullet form or in a table similar to the one below.
 
{| class="wikitable"
|-
! Ref !! Function !! Test Objective !! Evaluation Criteria !! Test Type !! Owners
|-
| 1 || Permission requirement for Pointer lock API was disabled || The test objective is to demonstrate that Pointer lock API is enabled without Permission request || Permission approval is not requested when try to access Pointer Lock API  || Manual || Eng Team
|-
| 2 || Warning bar is displayed when pointer lock is activated || The test objective is to demonstrate that when Pointer lock API is activated, a warning message: "<site> has control of your pointer. Press Esc to take back control." is displayed || Correct warning messages is displayed when Pointer Lock API is activated || Manual || Eng Team
|-
| 3 || Pointer lock functionality without full screen || The test objective is to demonstrate that when Pointer lock API functionality is correct without full screen enabled || Pointer lock API functions correctly || Manual || Eng Team
|-
| 4 || Pointer lock functionality with full screen enabled || The test objective is to demonstrate that when Pointer lock API functionality is correct with full screen enabled. Warning message for Pointer lock is not displayed, only the full screen warning is displayed|| Pointer lock API functions correctly under full screen || Manual || Eng Team
|-
| 5 || Pointer lock accessibility || The objective of these test suites is to verify that the application is accessible. || Testing for accessibility includes: <br />
- testing using high Contract themes<br />
- Mouse-only <br />
- Keyboard-only
|| Manual || Eng Team
|}

Navigation menu