Coding QA Podcast: Episode 37 Installer Testing

Coding QA Podcast

In this episode Federico and Matthew talk about their experience testing installers. Taking from their experience testing the ASP.NET MVC installer, they share tips and advice for those faced with the challenge of testing the very first experience of many products: the installer.News: *C.

Running time
0h30m
File size
28.00MB

Download Original File | View original post

Episode synopsis

In this episode Federico and Matthew talk about their experience testing installers. Taking from their experience testing the ASP.NET MVC installer, they share tips and advice for those faced with the challenge of testing the very first experience of many products: the installer.

News:

Installer Testing

  • Before somebody gets to use a product, they have to get it into their machines. It is the first experience with a product.
  • When building an installer test plan start by brainstorming 4 general areas:
    • Pre-requisites. How does the installer check for requirements? Does it provide enough information if requirements are not met? Does it fail as soon as possible?
    • Installation: What files are copies and where? Registry changes? GAC changes? Folders created? IIS changes? Does it need to check the web?
    • Uninstall: Is everything rolled back completely? Is anything is supposed to be left behind?
    • Machine state: OS, bitness, other applications running, hardware, disk space, network access, permissions.
  • Based on these variables, start building combinations of scenarios.
  • Use additional heuristics for identifying and discussing special cases:
    • Interruptions: Machine goes into hibernation, unplug network cable, user cancels the installer.
    • Full circle: Snapshot the state of the machine before installing, make sure it is the same after uninstalling.
    • Side by Side: Previous versions of the software installed, multiple versions installed.
    • Reinstall/Repair: Reinstall multiple times, break the application and repair it.
    • Temp folder: what is written in the temp folder.
    • Unintended changes: Additional files in placed installation directory.
    • Partial installs: some of files that are meant to be installed are already present, some of the files that are meant to be removed are not there.

In our experience, installer testing is closer to scripted testing than exploratory testing.

 

 

You might also like...

Comments

Contribute

Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.” - Brian Kernighan