The testing is required on the installation software of an operating system. The target hardware does not contain any existing software or an existing operating system. The installation is aimed for raw hardware.
The operating system can be installed by using the installation wizard or by following the instructions detailed in the installation manual.
The overall testing approach taken in this scenario is a two-stage approach. Firstly an installation test stage is performed. This is followed by a functionality test stage. For the purposes of this standard only the first stage is documented. The overall installation testing objective is to measure the installation against defined acceptance criteria and requirements, including to measure the successful installation of the operating system. This includes all aspects of system and software configuration.
Valid and invalid hardware platforms are required, with no software or existing operating systems present. It must be possible to refresh the environment to its initial state when required. The capability for performing a post-installation audit check must be available. All necessary and required devices and storage mediums must be present in the valid hardware platform.
AC101 - The operating system can be successfully installed by following the instructions in the installation manual
AC102 - The operating system can be successfully installed using the installation wizard
AC103 - The installation wizard contains clear and understandable processes and information instructions according to specified requirement
AC104 - All system configuration settings and file additions will be present according to the specified requirement
AC105 - The user can select pre-determined applications and use them to perform basic tasks successfully
AC106 - The installation wizard can successfully identify an invalid hardware platform and notify the user accordingly
AC107 - When the system boots up it will recognise the device required by the operating storage medium system
The installation tester will be an experienced technician with skills similar to the target Installation Engineer.
Measure the validity of the installation manual against the actual installation procedure.
The scope of the test case is the execution of the installation scripts and following the installation procedures from the manual.
AC101 - The operating system can be successfully installed by following the instructions in the installation manual
The installation manual must be present. An appropriate hardware platform containing no existing operating software must be available. All necessary and required access devices and storage mediums must also be available. Software and hardware must be ready and available for installation.
1. Boot the machine and establish what devices are detected from its boot profile. The information will be displayed on the screen as the boot profile is executed.
2. Depending on the result of recognising drive devices and on what medium the operating system is stored on, CD, disk or tape, create a boot file that will aid the boot profile.
3. The boot file will have to identify the necessary device on the hardware. Place the necessary storage medium (containing the operating system software), disk or tape, in the device and proceed with accessing the drive by using the basic DOS or boot language.
4. Identify the installation scripts on the drive and execute the necessary set-up scripts to start the installation of the operating system according to the installation manual.
5. If hard drive disk partitioning is necessary, plan accordingly on sizing and installation of necessary file systems. This will be specified in the installation manual.
6. Perform system information checks to determine all areas of the operating system have been installed. This will be specified in the installation manual.
7. Check configuration settings according to the installation manual with regard to security, permission, caching memory, etc.
8. Set-up procedures for preparing recovery disk when prompted by the installation procedure.
The installation procedures required during the actual installation correspond to those in the manual. (AC101)
Measure the usability of the installation wizard.
The scope of the test is the execution of the installation scripts and following the installation wizard.
AC102 - The operating system can be successfully installed using the installation wizard
AC103 - The installation wizard contains clear and understandable processes and information instructions according to specified requirement
The installation wizard must be available. An appropriate hardware platform containing no existing operating software must be available. All necessary and required access devices and storage mediums must also be available. Software and hardware must be ready and available for installation.
1. Boot the machine and establish what devices are detected from its boot profile. The information will be displayed on the screen as the boot profile is executed.
2. Depending on the result of recognising drive devices and on what medium the operating system is stored on, CD, disk or tape, create a boot file that will aid the boot profile.
3. The boot file will have to identify the necessary device on the hardware. Place the necessary storage medium (containing the operating system software), disk or tape, in the device and proceed with accessing the drive by using the basic DOS or boot language.
4. Identify the installation wizard scripts on the drive and execute the necessary set-up scripts to start the installation of the operating system, using the installation wizard.
5. If hard drive disk partitioning is necessary, plan accordingly on sizing and installation of necessary file systems. The user will be guided by the installation wizard to achieve this.
6. Perform system information checks to determine all areas of the operating system have been installed. The user will be guided by the installation wizard to achieve this.
7. Check configuration settings with regard to security, permission, caching memory, etc. The user will be guided by the installation wizard to achieve this
8. Set-up procedures for preparing recovery disk when prompted by the installation wizard.
The installation procedures required during the actual installation correspond to those achieved using the installation wizard. (AC102)
The installation wizard must contain clear and understandable processes and information instructions according to specified requirement. (AC103)
Note: Usability is measured according to specified requirements. This standard does not aim to duplicate usability testing, which is covered in a separate section of this standard.
Measure the system configuration according to the operating system set-up requirements
The scope of this test case is the system configuration itself.
AC104 - All system configuration settings and file additions will be present according to the specified requirement
The installation must have completed successfully according to the installation wizard.
1. Identify all necessary configuration files and settings according to the specification
2. Locate all files and settings and verify the values accordingly
All system configuration settings and file additions must be present and correct according to the specified requirement. (AC104)
Measure the successful installation and execution of applicable application software.
The scope of this test case is to install additional software compliant with the operating system and execute the selected software to perform basic tasks, though not going into functionality testing.
AC105 - The user can select pre-determined applications and use them to perform basic tasks successfully
The installation wizard must have completed successfully
Install additional application software compliant to the operating system and execute that software to determine if there are any failures on the operating systems' caching or memory functionality (Not going to far, that would be functionality testing).
The selected application must execute successfully. (AC105)
Perform negative testing to measure the error notification functionality of the installation wizard.
The scope of this test case is to:
· Identify installation scripts
· Execute scripts
· Monitor and note any information displayed on screen
· Validate error messages and information according to necessary specifications
AC106 - The installation wizard can successfully identify an invalid hardware platform and notify the user accordingly
An invalid hardware platform must be prepared for installation
1. Boot the machine and establish what devices are detected from its boot profile. The information will be displayed on the screen as the boot profile is executed.
2. Depending on the result of recognising drive devices and on what medium the operating system is stored on, CD, disk or tape, create a boot file that will aid the boot profile.
3. The boot file will have to identify the necessary device on the hardware. Place the necessary storage medium (containing the operating system software), disk or tape, in the device and proceed with accessing the drive by using the basic DOS or boot language.
4. Identify the installation scripts on the drive and attempt to execute the necessary set-up scripts to start the installation of the operating system using the installation wizard.
The installation wizard must identify the error and notify the users with the necessary information. (AC106)
Measure the device recognition required for storage medium access
The scope of the test case is device recognition.
AC107 - Device recognition is performed automatically by the operating system
All necessary devices and storage mediums must be present in hardware
1. Boot the machine
2. Identify from the boot information on the screen what devices are recognised
3. If required, prepare a boot file that points towards the required device for the operating system storage medium
4. Place the storage medium in the device
5. Access the device
6. Locate and execute the installation scripts
When the system boots up, it will recognise the device required by the operating system storage medium. (AC107)
Valid and invalid hardware is to be used during testing. The target hardware will not contain any existing software or an existing operating system. It must be switched on with all necessary cables and be ready to function up to its general boot capability.
Note: It is not necessary to carry out a pre-installation audit check in this test scenario as new hardware is involved and no software or existing operating system will be present.
Performed by the Installation tester.
The above test cases will be executed and the actual results matched against the expected results.
A post-installation audit check will be conducted against a predetermined list to ensure that all software and files present are as expected.
The completion criteria of the installation testing in this scenario will be measured in terms of the following:
· Were the acceptance criteria defined earlier measured satisfactorily?
· Were the results of the post-installation audit check satisfactorily?
After installation was the operating system:
· Resident and running?
· Resident and not running?
· Not resident and run-able?
· Not resident and not run-able until installed?
A home/small office package vendor sells a drawing package. This is available to run on a number of operating systems. Only a small number of operating systems are advertised as supported by the vendor.
The primary installability requirements are defined by the designers in terms of the target platform(s) and the version of the software to be installed.
A new installation process is to be tested, with specific versions of the package on specific platforms:
|
Ins Req 1 |
Version 5.2 is the version most used in the field at present, and is supported on Operating system A v2.1 and Operating system A v3.0. |
|
Ins Req 2 |
Version 6.0 is the latest version and is only supported Operating system A v3.0. |
|
Ins Req 3 |
Version 6.1 is the same as version 6.0 in functionality, but is re-engineered for installation on the operating system B v4.0. This is the first version to be available on platforms other than operating system A family. Earlier versions of operating system B are not supported. |
|
Ins Req 4 |
On operating system A upgrade from current and the last supported versions must be possible. |
In discussion between the designers, the installability testers and the usability group, additional installability requirements are identified. These are based on identifying the contexts of use for the package and the likely profile of the installer.
¨ Typical customers will be installing and using the package in a home or small office.
¨ Their experience of IT, the platform they are using, installing packages, and of this particular package may be very low.
¨ There will also be very experienced customers installing and using the package.
¨ The target system configuration may be the minimum specified in the sales material for the package, and it is possible that some customers will try to install on a system with less than the minimum configuration.
¨ Customers will want to get "up and running" with the package as quickly as possible.
The additional installability requirements identified are:
Target system configuration:
|
Ins Req 5 |
The installation process must complete within 2 minutes on the minimum memory/processor test platforms set up in the test laboratory. |
|
Ins Req 6 |
An attempt to install with less than the minimum configuration in the target system will result in an understandable error message |
Installation process (as described in the installation manual or guidelines):
|
Ins Req 7 |
The installation wizard should have fewer than 6 steps. |
|
Ins Req 8 |
Either the package will install and run, or an understandable error message will be produced. |
|
Ins req 9 |
It must be possible to cancel the install and to uninstall |
People who will carry out the installation:
|
Ins Req 10 |
Instructions must be in clear non-technical language. |
|
Ins Req 11 |
A typical customer should be able to complete the installation and the tutorial in 30 minutes. |
|
Ins Req 12 |
The tutorial is optional, but is offered as part of the installation wizard. |
The group then identify high-level acceptance criteria from the requirements:
|
Ins Req 1 |
Version 5.2 is the version most used in the field at present, and is supported on Operating system A v2.1 and Operating system A v3.0. Acceptance criteria: · Version 5.2 can be installed to Operating system A v2.1 · Version 5.2 can be installed to Operating system A v3.0. |
|
Ins Req 2 |
Version 6.0 is the latest version and is only supported on Operating system A v3.0. Acceptance criteria: · Version 6.0 can be installed on Operating system A v3.0. · Version 6.0 cannot be installed on Operating system A v2.1 · The error message when attempting to install v6.0 on Op sys A v2.1 is understandable |
|
Ins Req 3 |
Version 6.1 is the same as version 6.0 in functionality, but is re-engineered for installation on the operating system B v4.0. This is the first version to be available on platforms other than operating system A family. Acceptance criteria: · Version 6.1 can be installed to Operating system B v4.0 · Version 6.1 cannot be installed on Operating system A · The error message when attempting to install v6.1 on Op sys A is understandable |
|
Ins Req 4 |
On operating system A upgrade from current and the last supported versions must be possible. Acceptance criteria: · V6.0 cannot be installed to Operating system A v2.1 with v5.2 already installed · The error message when attempting to install v6 on Op sys A v2.1 is understandable · V6.0 can be installed to Operating system A v3.0 with v5.2 already installed · V5.2 can be installed to Operating system A v2.1 with v4 already installed · V5.2 can be installed to Operating system A v3.0 with v4 already installed |
|
Ins Req 5 |
The installation process must complete within 2 minutes on the minimum memory/processor test platforms set up in the test laboratory. Acceptance criteria: · On all versions installation must complete within 2 minutes on a minimum configuration |
|
Ins Req 6 |
An attempt to install with less than the minimum configuration in the target system will result in an understandable error message. Acceptance criteria: · On all versions an understandable warning must be given if an attempt is made to install below the minimum configuration |
|
Ins Req 7 |
The installation wizard should have fewer than 6 steps. Acceptance criteria: · Wizard has fewer than 6 steps |
|
Ins Req 8 |
Either the package will install and run, or an understandable error message will be produced. Acceptance criteria: · All error messages are produced during usability testing and are understood by 100% of usability participants · On all versions an understandable warning must be given if an attempt is made to install below the minimum configuration |
|
Ins Req 9 |
It must be possible to cancel the installation and to uninstall ¨ Cancellation is possible at any installation wizard step until the final step is started ¨ Cancellation or Uninstall before the tutorial or use of the package should restore the system to configuration as before installation started ¨ Cancellation after the tutorial or other use is possible but will only uninstall components not used by other packages/programs |
|
Ins Req 10 |
Instructions must be in clear non-technical language. Acceptance criteria: · 95% or more of the usability test participants express satisfaction with the clarity and ease of the installation |
|
Ins Req 11 |
A typical customer should be able to complete the installation and the tutorial in 30 minutes. Acceptance criteria: · All the usability test participants are able to complete the installation and tutorial in less than 30 minutes without help other than that offered by the wizard and tutorial |
|
Ins req 12 |
The tutorial is optional, but is offered as part of the installation wizard. Acceptance criteria: · The tutorial is offered during the wizard after the installation, with a "yes" / "no" choice for the installer · The tutorial starts automatically if "yes" is selected · If "no" is selected the wizard closes, leaving the package ready to use |
The installation of the package must be tested in its different versions on the different platforms. Because the package might be purchased for installing on a range of platforms, it is decided that testing and support will be limited to a small number of platforms, but that part of the testing is to ensure that this is clear. The installability testers draw up matrices to show target system configurations, operating system versions and package versions for a new installation and for an upgrade. Not all combinations will be tested, and a risk based discussion takes place between the installability testers, the designers and the help desk to decide which options to test and which to leave. For example:
¨ Version 6.1 is not available as an upgrade version so this option does not have to be tested. In later versions, an additional test to check the upgrade can only be used with a machine where the package has been installed.
¨ Only V4.0 of operating system B is supported, earlier versions are not supported. These earlier versions of the operating systems will not be shown in the test matrices, but the marketing material and packaging for version 6.1 will be checked, as well as the user guide, to ensure that it is clear that earlier versions are not supported.
¨ Not all combinations of platform and package version will be tested.
The key to the matrices is:
· "error 1" is message "you need version 6.1 for this platform – please ring (number) or visit or web-site (address) for replacement"
· "error 2" is message "you need version 6.0 for this platform – please ring (number) or visit or web-site (address) for replacement"
· “error 3” is message “you cannot install an upgrade as the previous version is not installed on this machine – please ring (number) or visit or web-site (address) for replacement full installation diskette”
· "error 4" is message "you need v5.2 for this platform - please ring (number) or visit web-site (address) for replacement"
· "warning 1" is message "your machine is not as powerful as the recommended minimum for using this package. You will be able to install but you may find the package is slow. If you want more advice, please ring (number) or contact your retailer for advice."
· "Able to install" means able to follow the wizard and install successfully without recourse to activities not described in the wizard, and then carry out the beginner's tutorial successfully within the required time-scales.
Matrix 1: System status: New Install
(Requirements 5, 7, 8, 10, 11, 12 apply generally)
|
Platform: |
||
|
Version: |
Op sys A v2.1 - Minimum configuration |
Op sys A v3.0 - Minimum configuration |
Op Sys B V4.0 - Minimum configuration |
5.2 - Req 1 |
able to install |
able to install |
Do not test |
6.0 - Req 2 |
error 4 |
able to install |
error 1 |
6.1 - Req 3 |
Do not test |
error 2 |
able to install |
Matrix 2: System status: Upgrade
(Requirements 5, 7, 8, 10, 11, 12 apply generally)
|
Platform: |
|
Version: |
Op sys A v2.1 - Minimum configuration |
Op sys A v3.0 - Minimum configuration |
5.2 - Req 4 |
upgrade from 4.0, able to install |
upgrade from 4.0, able to install |
6.0 - Req 4 |
upgrade from 5.2, error 4 |
upgrade from 5.2, able to install |
6.1 - Req 4 |
Do not test |
upgrade from 5.2, error 2 |
5.2 - Req 4 |
Do not test |
not installed, attempt to upgrade, error 3 |
6.0 - Req 4 |
not installed, attempt to upgrade, error 3 |
Do not test |
6.1 - Req 4 |
Do not test |
not installed, attempt to upgrade, error 3 |
Matrix 3: System status: New Install - less than minimum configuration
(Requirements. 7, 8, 10, 11, 12 apply generally)
|
Platform: |
||
|
Version: |
Op sys A v2.1 - Less than Minimum configuration |
Op sys A v3.0 - Less than Minimum configuration |
Op Sys B V4.0 - Less than Minimum configuration |
5.2 - Req 6 |
warning 1 |
Do not test |
Do not test |
6.0 - Req 6 |
Do not test |
warning 1 |
Do not test |
6.1 - Req 6 |
Do not test |
Do not test |
warning 1 |
Matrix 4: System status: Upgrade - less than minimum configuration
(Requirements. 7, 8, 10, 11, 12 apply generally)
|
Platform: |
|
Version: |
Op sys A v2.1 Less than Minimum configuration |
Op sys A v3.0 Less than Minimum configuration |
5.2 - Req 6 |
warning 1 |
Do not test |
6.0 - Req 6 |
Do not test |
warning 1 |
Matrix 5: Ability to cancel the installation, the tutorial, and to uninstall
(Requirement 9, 11, 12)
|
Platform: |
|||
Test to do: |
Op sys A v2.1 Minimum configuration |
Op sys A v3.0 Minimum configuration |
Op sys B v4.0 Minimum configuration |
|
|
Step 1 cancel |
V5.1 |
V5.1 |
V6.0 |
V6.1 |
|
Step 2 cancel |
Do not test |
V6.0 |
V6.1 |
|
|
Step 3 cancel |
Do not test |
V6.0 |
V6.1 |
|
|
Step 4 cancel |
Do not test |
V6.0 |
V6.1 |
|
|
Step 5 cancel |
Do not test |
V6.0 |
V6.1 |
|
|
Step 6 cancel |
V5.1 |
V5.1 |
V6.0 |
V6.1 |
|
Uninstall before tutorial or use |
V5.1 |
V6.0 |
V6.1 |
|
|
Uninstall after tutorial |
Do not test |
V6.0 |
V6.1 |
|
|
Uninstall after use |
Do not test |
V6.0 |
V6.1 |
|
|
Uninstall after tutorial and use |
V5.1 |
V6.0 |
V6.1 |
|
|
Install and cancel tutorial |
V5.1 |
V5.1 |
V6.0 |
V6.1 |
|
Install and run tutorial, cancel part way |
V5.1 |
V5.1 |
V6.0 |
V6.1 |
|
Install and run tutorial all through |
Covered in other matrices |
|||
The installation tester will ideally have the same level of expertise as the target installer. However this is unlikely given the working environment the test group is likely to be from. Therefore the usability group will be asked to carry out some usability testing, selecting suitable participants.
Tests will be carried out by the following teams:
1. The installability testers will test all the agreed test cases, to cover all of the matrices, on minimum configuration machines and for the machines with less than the minimum configuration. This will provide expert level timings and test the functionality of the install for new and upgrade installation.
2. The usability group will carry out usability tests for the installation to understandability and efficiency for the users. The usability group will select both the user sample and the platform sample by analysing the context of use (see Usability section). This will include observing the participants reaction to the Wizard and to all the errors and warnings, and commenting on their understandability.
· All identified versions of the package must be available.
· All required platforms must be available and in the required state.
· It must be possible to refresh the environment to its initial state when required.
· The capability for performing both pre and post-installation audit checks on all test environments must be available.
· The capability for recording the installation /upgrade and tutorial run through timings must be available and its degree of accuracy known.
Test cases are identified to measure the installability requirements and acceptance criteria identified above, with a test case for each cell in the matrices that requires a test. Only the seven test cases for the first of the matrices are shown below; in fact, test cases would be drawn up for all the matrices.
Matrix 1: System status: New Install (Requirements 5, 7, 8, 10, 11, 12 apply generally)
|
Platform: |
||
Version: |
Op sys A v2.1 - Minimum configuration |
Op sys A v3.0 - Minimum configuration |
Op Sys B V4.0 - Minimum configuration |
5.2 - Req 1 |
Test case 1 |
Test case 2 |
Do not test |
6.0 - Req 2 |
Test case 3 |
Test case 4 |
Test case 5 |
6.1 - Req 3 |
Do not test |
Test case 6 |
Test case 7 |
Note: In these test cases, when the test case results in the installation completing, the whole tutorial will be exercised. Cancelling the tutorial will be tested as part of matrix 5.
Matrix 1 Test case 1:
The start/entry state |
Op sys A v2.1 - Minimum configuration – no previous install of this package |
Which Installability requirement/acceptance criterion is being tested |
Able to install v5.2 on Operating system A v2.1 machine as a new install Reqs: 1, 5, 7, 8, 10,11, 12 |
The actions and inputs |
Test steps: Switching on the machine and booting as normal Check the labelling on the box, user guide, installation instructions and CD: are the target platform, version and minimum system requirements clearly stated? Insert the installation CD in the CD ROM drive Follow the instructions in the Install wizard Run the beginner's tutorial from the user guide |
The expected outcome |
R1, R5, R7: The install is completed successfully in fewer than 6 steps, completing within 2 minutes. R8, R10, R11, R12: The installer (tester or usability participant) is able to understand any messages and instructions from the wizard. Usability participants are able to complete the installation and tutorial in less than 30 minutes. |
Matrix 1 Test case 2:
The start/entry state |
Op sys A v3.0 - Minimum configuration– no previous install of this package |
Which Installability requirement/acceptance criterion is being tested |
Req 1, 5, 7, 8, 10,11,12 Install v5.2 to Op Sys A v3.0 |
The actions and inputs |
Test steps: Switching on the machine and booting as normal Check the labelling on the box, user guide, installation instructions and CD: are the target platform, version and minimum system requirements clearly stated? Insert the installation CD in the CD ROM drive Follow the instructions in the Install wizard Run the beginner's tutorial from the user guide |
The expected outcome |
R1, R5, R7: The install is completed successfully in fewer than 6 steps, completing within 2 minutes. R8, R10, R11, R12: The installer (tester or usability participant) is able to understand any messages and instructions from the wizard. Usability participants are able to complete the installation and tutorial in less than 30 minutes |
Matrix 1 Test case 3:
The start/entry state |
Op sys A v2.1 - Minimum configuration– no previous install of this package |
Which Installability requirement/acceptance criterion is being tested |
Req 2, 5, 7, 8, 10 Not able to install v6.0 to op sys A v2.1 |
The actions and inputs |
Test steps: Switching on the machine and booting as normal Check the labelling on the box, user guide, installation instructions and CD: are the target platform, version and minimum system requirements clearly stated? Insert the installation CD in the CD ROM drive Follow the instructions in the Install wizard |
The expected outcome |
R2, R5, R7 Error 4 on start of install Install stops - no change to system R8, R10: The installer (tester or usability participant) is able to understand any messages and instructions from the wizard. |
Matrix 1 Test case 4:
The start/entry state |
Op sys A v3.0 - Minimum configuration– no previous install of this package |
Which Installability requirement/acceptance criterion is being tested |
Req 2, 5, 7, 8, 10,11, 12 Install v6.0 to op sys A v3.0 |
The actions and inputs |
Test steps: Switching on the machine and booting as normal Check the labelling on the box, user guide, installation instructions and CD: are the target platform, version and minimum system requirements clearly stated? Insert the installation CD in the CD ROM drive Follow the instructions in the Install wizard Run the beginner's tutorial from the user guide |
The expected outcome |
R2, R5, R7: The install is completed successfully in fewer than 6 steps, completing within 2 minutes. R8, R10, R11, R12: The installer (tester or usability participant) is able to understand any messages and instructions from the wizard. Usability participants are able to complete the installation and tutorial in less than 30 minutes |
Matrix 1 Test case 5:
The start/entry state |
Op Sys B V4.0 - Minimum configuration– no previous install of this package |
Which Installability requirement/acceptance criterion is being tested |
Req 2, 5, 7, 8, 10 not able to install v6.0 on op sys B |
The actions and inputs |
Test steps: Switching on the machine and booting as normal Check the labelling on the box, user guide, installation instructions and CD: are the target platform, version and minimum system requirements clearly stated? Insert the installation CD in the CD ROM drive Follow the instructions in the Install wizard |
The expected outcome |
R2, R5, R7 Error 1 on start of install Install stops - no change to system R8, R10: The installer (tester or usability participant) is able to understand any messages and instructions from the wizard. |
Matrix 1 Test case 6:
The start/entry state |
Op sys A v3.0 - Minimum configuration– no previous install of this package |
Which Installability requirement/acceptance criterion is being tested |
Req 3, 5, 7, 8, 10 Not able to install v6.1 to Op Sys A |
The actions and inputs |
Test steps: Switching on the machine and booting as normal Check the labelling on the box, user guide, installation instructions and CD: are the target platform, version and minimum system requirements clearly stated? Insert the installation CD in the CD ROM drive Follow the instructions in the Install wizard |
The expected outcome |
R3, R5, R7 Error 2 on start of install Install stops - no change to system R8, R10: The installer (tester or usability participant) is able to understand any messages and instructions from the wizard. |
Matrix 1 Test case 7:
The start/entry state |
Op Sys B V4.0 - Minimum configuration– no previous install of this package |
Which Installability requirement/acceptance criterion is being tested |
Req 3, 5, 7, 8, 10, 11, 12 Able to install v6.1 to op sys B |
The actions and inputs |
Test steps: Switching on the machine and booting as normal Check the labelling on the box, user guide, installation instructions and CD: are the target platform, version and minimum system requirements clearly stated? Insert the installation CD in the CD ROM drive Follow the instructions in the Install wizard Run the beginner's tutorial from the user guide |
The expected outcome |
R3, R5, R7: The install is completed successfully in fewer than 6 steps, completing within 2 minutes. R8, R10, R11, R12: The installer (tester or usability participant) is able to understand any messages and instructions from the wizard. Usability participants are able to complete the installation and tutorial in less than 30 minutes |
The remaining matrices would have tests cases prepared in the same way.
All identified versions of the package must be available.
All required platforms must be available and in the required state.
A pre-installation audit check will be conducted on all test environments to establish a base list to be checked against after the post-installation audit check has been performed.
The installation tester performs the installation manual review.
The installation wizard should have fewer than 6 steps. Instructions must be in clear non-technical language.
The test cases will be executed and the actual results matched against the expected results.
A post-installation audit check will be conducted on all test environments. This will be matched to the results of the pre-installation audit check to ensure that all software and files present are as expected.
The completion criteria of the installation testing in this scenario will be measured in terms of the following:
· Were the acceptance criteria defined earlier measured satisfactorily?
· Were the results of the pre and post-installation audit check satisfactorily?
· After installation / upgrade is the package resident and run-able?