Click to edit Master title style

Date :
17/02/2012 Quality Assurance Training

Narendra Nalamwar

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Session Objectives
Summary:
– Understand What is quality and it’s importance
– Understand how to conduct a Quality Check of Installer products
– Understand what are MSI best practices
– Understand how to validate Installer products using orca
– How to improve the quality of installer products

Day Wise Duration:

Day 1- Complete QA Process .

Target Audience:
IT Engineers with understanding of basic Windows installer concept and
Repackaging.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Table
• Quality assurance overview
• How to check the quality (Installshield) :
– Installation expert
– MSI script
– Setup editor
• How to check the quality (orca)
– Validation

COMMERCIAL IN CONFIDENCE
3
© Copyright 2011 ECS Europe Limited
 Click to edit Master
Quality Assurance Overview title style

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Quality Assurance Overview
What is Quality ?

• Quality is a characteristic that a product or service must have.

• Products must be reliable, useable, and repairable.

• The most important qualities are the ones that customers want.

• So a quality product or service is one that meets the needs and expectations
of our customers.

What is Quality Assurance ?

• Quality Assurance (QA) is defined as a set of activities whose purpose is

to demonstrate that an entity meets all quality requirements.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

 Click to edit Master title
Quality Check For Installer Product
style

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

QA Check For Installer Product

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Product Details
• Use the General Settings area of the General Information view to specify details
such as product name and product version.

• Data is displayed for .MSI, .ISM, and .MST files.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Add or Remove Programs
Add or Remove Programs settings in the General Information view.
Some Add or Remove Program related Properties are:
1) ARPNOMODIFY
2) ARPNOREMOVE
3) ARPCOMMENTS
4) ARPNOREPAIR
5) ARPSYSTEMCOMPONENT = 0

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Features
Feature in Legacy Application :
To prevent packages from being unnecessarily complex, and to ensure self-repair
works correctly, any legacy applications should only have a single feature(called
Complete feature), unless multiple features are specifically required for some
reason, in which case should be in the delivery documentation

Features in Vendor application :

Should have a new feature called “ECSAdditions” to avoid altering the existing feature
structure.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

File

Check for below point in File and Folder view tab,

• Application related files.

• INSTALLDIR.

• Unwanted files.

• Services file.

Continue….

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

File Exclusion List
Files that need to be removed from the application.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Registry

Check for below point in Registry view tab,

• Unwanted registries.

• User specific registries.

• Audit keys.

• Run key.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Registry Exclusion List
Registries that need to be removed from the application.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

INI File
All .ini files should be checked to ensure the changes being made are relevant to the
application captured. A check should also be made to ensure that the INI files are
captured in the correct locations. INI files should only be installed as files when they
do not conform to INI file standards.

• Garbage ini files.

• Proper ini files format.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Shortcuts
All application shortcuts should be located in the public profile

All applications containing multiple shortcuts should be placed in:

Start Menu\Programs\<vendor>\<shortcut>

Continue…

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Shortcuts
All applications containing a single shortcut should be placed in:
Start Menu\Programs\<shortcut>
e.g. Start Menu\Programs\Adobe Reader 9

Unless specifically stated in the PRF, Shortcuts for the following types of file should not
be included in re-captured packages and should be removed from vendor packages via
the related transform.

Help files
Log Files
Online Registration
Documentation files
Readme files
Uninstall scripts
Vendor URLs etc. COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited
Environment Variable
• Select the Environment Variables item in the System Configuration
section then review the include items.
• All variables should be set as system variable type.
• the [~] value should precede any additional data added by the
application so that existing values will not be overwritten.
• Make sure that the all variables are set to append to the existing value if
necessary and are removed on uninstall
• Unwanted variables.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

ODBC
The package should not contain any redundant registry keys or INI file entries related to
ODBC entry creation or modification.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Custom Actions and Sequences
• Custom actions named, sequenced properly.
• All custom actions should be documented in the Custom Actions
/Scripts section of the Readme.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Important MSI Properties
• All below properties should be present in the application.

• Check Public properties which are used for replacing the hardcoded values in the
application such as port, server name, computer etc.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Components
Microsoft’s best practices should be adhered to for the creation of all components. These
include the following:

• Every component must have a defined key path.

• No component should contain more than one versioned file e.g. .DLL, .OCX, .TLB, .EXE.

• No two components should install the same resource under the same name and target
location.

• Only one file per component can be the target of a desktop or program menu shortcut.

• Newer versions of components must be backwards compatible with previous versions of

the component.

• Each component will have its own unique identifier (GUID).

• Put registry keys associated with files or components in matching component

• Put Current User registry keys in their own component and non-Current User registry keys
in their own component COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited
Components
Component configurations.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Components
Components attributes (8/16/24) :
INSTALLDIR File Component : 0
Registry key component : 4
Shared Component : 8
Permanent Component : 16
Shared and permanent Component : 24

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Media Details
• Media table decides how to compress files.
• For internal Cabs (cab compressed within MSI), media table entry begins
with “#” sign. Media table entry without “#” sign indicates external cab
file (Cab out side MSI).

Internal Cab File

External Cab File

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

MSI Tables
• LockPermission Table – should be blank.

• RemoveFile Table – values 1/2/3.

• RemoveRegistry Table – value 1 (not preferable).

• SelfReg Table – blank in legacy. Needs to be documented if present in vendor.

• Upgrade Table – If application is an upgrade only then should entries be

present.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Basic MSIStandards
• Hard coded path : Replace with Public properties if hardcoded entry in
the application.

• Component : No Empty component and all component should have

keypath.

• INI : INI file should be pass through INI file table.

• Shortcut : Proper working directory and advertise.

• Files and registries : No Unwanted files and registries should be

present in the application.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Lab 1
Conduct QA for an application “WinZip_14.0.8_EN” (application which worked for
Vendor )with the help of QA documents.

Lab Time: 60 mins.

1. Use the proper QA Checklist to check the quality of package.

2. Start QA.
3. Note down all the bugs found during QA.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

 Click to edit Master title style
Quality Check For Installer Product (Orca)

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

QA Check For Msi Using Orca
Orca is the windows installer table editor tool, which is used to edit and validate
the MSI database.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

 Click to edit Master
Validation Using Orca title style

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Validate The Package Using Orca

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

ICE - Validation
• Tools – Orca and Wise package studio.

• Error resolution –

» Legacy application (All)

» Vendor application (resolve introduce by transform).

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

Lab 2

Conduct QA for an application “WinZip_14.0.8_EN” Using ORCA and with

the help of QA documents.

Lab Time: 60 mins.

1. Copy the application “WinZip_14.0.8_EN”, to your desktop.

2. Use the proper QA Checklist to check the quality of package.
3. Start QA.
4. Note all the bugs found during QA.

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited

COMMERCIAL IN CONFIDENCE © Copyright 2011 ECS Europe Limited