It’s been almost a
year that when I last added a blog post to Software Quality Geeks. Quickly
getting towards the topic that today we will be having a look at Installation
Testing. This blog post or next few ones, probably soon after this one, will
have the same theme that rather than writing too much about the topic we should
have a look at bird eye view of any quality or testing topic. Therefore, we
will be learning at installation/un-installation testing and its coverage area
with help of mind-map or brainstorming diagram.
Installation Testing
is very import part of any software, because it usually requires some of sort
of changes in customers or end-users machines so it must be tested carefully.
Since this is the point when customer first communicates with your application,
anything that goes awry at this time can cause enough damage to the business.
Therefore, to avoid any potential loss to the business Installation
Testing/un-installation testing should be a part of Test Plan and given enough
time in testing the application as far as Installation/un-installation is concerned
and for that following map can be referred and customized according the need,
budget and timeframe.
The post is not open
to comments, must provide your valuable ones.
Good luck for
installation testing!
