Installability Testing: Complete Guide for ISTQB Advanced Level Test Analyst (CTAL-TA)
Introduction
Installability testing checks whether software can be correctly and efficiently installed, upgraded, configured and uninstalled in its intended target environments. It is one of the quality characteristics covered in ISTQB Advanced Level material on testing non-functional quality characteristics.
Where it fits in the syllabus
In ISO/IEC 25010, installability is a sub-characteristic of portability. Portability has three sub-characteristics:
- Adaptability: the software can be adapted to different hardware, software or other operational environments.
- Installability: the software can be successfully installed and uninstalled in a specified environment.
- Replaceability: the software can replace another specified software product for the same purpose in the same environment.
In the current ISTQB Advanced syllabi, portability testing (including installability) sits mainly with the Technical Test Analyst. However, the Test Analyst often contributes, especially where installation affects the user. Examples include the usability of installation wizards, the correctness of installation manuals, and functional checks after installation. You should know the concept, its sub-characteristic relationships and typical test conditions for either role.
Why installability testing is important
- First impression: installation is often the user's first contact with the product. A failed or confusing installation can lead to abandonment, support calls and reputational damage.
- System integrity: a faulty installer can corrupt the operating system, overwrite shared libraries (DLLs), break other applications or leave the environment unstable.
- Diverse environments: software is deployed across many combinations of operating systems, versions, hardware, browsers, databases and permission levels. Installation must succeed on all supported targets.
- Upgrades and maintenance: patches, upgrades and rollbacks must preserve user data and configuration. A failed upgrade in production can cause major outages.
- Cost and risk reduction: finding installation defects before release avoids expensive field failures, emergency patches and the cost of manual recovery.
- Contractual and regulatory needs: some domains require documented, repeatable and verified installation procedures.
What installability testing covers
Typical objectives, in line with ISTQB guidance:
1. Successful installation on all target environments: validate that the software installs by following the instructions in the installation manual or wizard. This includes different operating systems, hardware configurations and installation options (typical, custom, minimal, full).
2. Handling installation failures: confirm that failures are handled correctly. Examples include partial installation, interrupted installation (power loss, network loss, user cancel), insufficient disk space, missing prerequisites and lack of administrator rights. The system should not be left in an undefined or corrupted state, and the user should receive clear messages.
3. Detecting environment damage: check that installation or uninstallation does not corrupt the operating system or other software, for example by overwriting shared components or modifying registry entries incorrectly.
4. Uninstallation: verify that removal is complete. Files, registry entries, services and shortcuts should be removed unless they are intentionally retained (such as user data). Other applications must not be affected.
5. Upgrades, downgrades, patches and repair: verify migration from previous versions, data and configuration preservation, rollback capability and repair functions.
6. Correctness of installation procedures and documentation: check that the manual, wizard and help texts are accurate, complete and understandable. Following them should actually lead to a working system.
7. Usability of the installation process: assess whether the installer is easy to understand and operate, and whether the options presented are meaningful. This area overlaps strongly with Test Analyst usability skills.
8. Installation time and effort: measure the time taken, the number of steps and the level of expertise required, and compare these against requirements.
9. Post-installation functionality: confirm that the installed software actually works, usually through smoke or sanity tests after installation.
How installability testing works
1. Analysis and planning
- Identify the supported target environments from the requirements (OS versions, hardware, prerequisite software, locales).
- Identify the installation types: fresh install, custom install, silent or unattended install, network or remote deployment, upgrade from version N-1 or N-2, patch, repair, uninstall.
- Use risk analysis to prioritise the environments and scenarios most used by customers, for example through operational profiles.
2. Test design
- Build an environment and configuration matrix. Because full combinations can explode, use combinatorial techniques such as pairwise testing or classification trees to select a representative subset.
- Design negative tests: low disk space, cancel mid-way, kill the process, disconnect the network, missing prerequisites, restricted user rights, an already-installed version, a corrupted installer package.
- Use checklists for files, registry or configuration entries, services, permissions and shortcuts that should exist after installation and be gone after uninstall.
- Write use-case or scenario-based tests that follow the installation manual step by step.
3. Test environment
- Use clean machines that match the target environments. Virtual machines and snapshots make it easy to reset to a known state.
- Also test on 'dirty' or realistic machines that already have other software and older versions installed.
- Use tools that capture system state before and after installation to detect unintended changes.
4. Execution and evaluation
- Run the installation scenarios, then smoke tests to confirm functionality.
- Compare system snapshots after uninstall against the original state.
- Record metrics: installation success rate, installation time, number of manual steps and defects found.
- Report defects in the installer, the documentation and environment side effects.
Example
A desktop accounting application supports Windows 10 and 11, in 32-bit and 64-bit versions, with three database options. Tests could include:
- A fresh typical install on each pairwise-selected configuration.
- An upgrade from version 4.2 that preserves the company ledger data.
- Cancelling the installation at 60% and verifying a clean rollback.
- Installing as a non-admin user and checking for a clear error message.
- Uninstalling and verifying that no residual services remain, while user data files are kept as specified.
- Following the printed manual exactly to verify that it is accurate.
Relationship with other characteristics
- Adaptability: whether the product works in different environments. Installability is about getting it installed and removed there.
- Replaceability: whether the product can replace another product. This often involves installation and data migration, but the focus is on substitution.
- Compatibility (co-existence): whether the product runs alongside other software without adverse effects. This overlaps with checking that installation does not damage other applications.
- Usability: the installation wizard is a user interface and can be evaluated with usability techniques.
- Reliability (recoverability): relevant when installation is interrupted and must recover.
Exam Tips: Answering Questions on Installability Testing
1. Know the hierarchy: installability is a sub-characteristic of portability (ISO 25010), alongside adaptability and replaceability. A question asking which characteristic is tested when 'software is installed on several operating systems following the manual' points to installability.
2. Spot the keywords: install, uninstall, upgrade, patch, setup wizard, installation manual, partial installation, rollback, installation time, residual files. These signal installability. 'Runs in a different environment without installation concerns' signals adaptability. 'Replaces an existing product' signals replaceability.
3. Remember the typical test objectives: successful install on all targets, correct handling of failures, no corruption of the OS or other software, correct uninstall, correct procedures and documentation, usability of the installer and measured installation time or effort. Wrong options often describe performance or security goals instead.
4. Negative scenarios matter: if an option mentions an interrupted or partial installation leaving the system in a defined state, it is usually a valid installability test.
5. Think about the role: questions may ask how a Test Analyst contributes. Good answers include checking installation documentation, the usability of the wizard and post-install functional verification. Deep system-level checks such as registry and DLL analysis lean towards the Technical Test Analyst.
6. Technique selection: when many environment combinations exist, the best answer usually involves combinatorial or pairwise testing, prioritised by risk or operational profile, rather than exhaustive testing.
7. Upgrades count: data and configuration preservation during upgrades is part of installability testing. Do not confuse it with pure data migration in replaceability questions unless replacement of another product is stated.
8. Read scenario questions carefully: identify the stakeholder concern first (for example 'users complain that setup takes too long and is confusing'). Then select the test that directly addresses it, such as measuring installation time and evaluating installer usability.
9. Eliminate distractors: options about response time under load (performance), unauthorized access (security) or mean time between failures (reliability) are rarely correct for installability questions.
10. Remember timing: installability testing is often done in system and acceptance testing in representative environments. It may also be included in continuous delivery pipelines through automated deployment tests.
Summary
Installability testing ensures that software can be installed, upgraded, configured and removed reliably, efficiently and safely across all supported environments. It covers both success and failure scenarios, documentation accuracy and installer usability. For the exam, link it to portability, recognise its keywords, know its typical objectives and choose risk-based and combinatorial approaches for environment coverage.
