Home » Software Testing » Manual Testing » Installation testing » Test Cases to test software update before its release

Test Cases to test software update before its release

Since we are familiar with the update notification in our windows and Ubuntu machines and every day when we connect with internet, we get update, notification for windows update near other system icons.

So lets start with the meaning of update and what is included in update and how it cause impact on the user experience after update

What is Update and what is included in update

Updates are additions to software  that can help to fix problem and bug and this also improves the performance of software along with the user experience.

Impact of updates

  • It helps to fix all bug those were not fixed in previous version of software

  • It increases the performance of software

  • It also increases the security aspect of software if it is related to sharing of data through it, like some software related to banking

  • Some time it also helps to add some extra feature in software

  • User interface sometime also improved by updating the software

  • Updates also increase the stability of software and we get solution of certain system crash due to software

Since update increases the user experience, then this is the responsibility of product company to test each and every  aspect of fix and enhancement before releasing update.

Here I am suggesting some test cases that will help tester to test fixes and enhancement package that is included in update

1- verify the way of update .

  • Automatic update : verify system check for update everyday at a fix time suppose i am taking 2 am time.
  • Manual Update: verify manual update check ( Go to help-> click on update link  and wait for few moment it will show update if update would be available).

2- Verify the version of software before every update.

3- Verify the version of software just after update ( version of software should increase I am taking the example of Adobe reader, suppose version before update is 9.5 and after update it starts showing 9.5.1).

4- Verify on clicking notification, update asks for Licensing agreement.

5- Verify installation should start just after accepting Licensing agreement (Some time EULA appears before update).

6- Verify installation should terminate after disagreeing with licensing agreement.

7- Verify error messages when disk space is low at time of installation of update( Error message should ask for disk clean-up).

8- Verify installation of update when internet connection get disconnected  and error message should appear for internet connection.

9- Verify proxy server from where update are being downloaded for installation.

10- Verify message something like this”Software is updated and there is no update present” when we try for manual update.

11- Verify compatibility of software if there is some conflict with certain software or hardware in earlier version.

12- Verify disk space used by update

13- Verify for effective implementation of update restart is needed

14- Verify the language at Licensing agreement page

15- Verify update at various kind of user like User with Admin privilege, user with standard user account and user for user with no permission to do any change in system configuration

16- Verify installation of update when firewall is on and security is high

17- Verify installation of update at  low-speed internet and at high-speed net

19- Verify uninstallation of software after update

20- Verify the uninstallation of software updates ( To make sure user could uninstall software updates if any thing goes wrong)

Also read : Installation Testing and Test cases for good installation testing- Installation Testing

7 thoughts on “Test Cases to test software update before its release”

  1. I think these test cases should also be taken in to account (http://testertested.blogspot.in/2007/07/why-is-testing-monotonous-unspoken.html)

    These test cases are advised by Pradeep Soundararajan to some tester and he has written this in one of his post

    1- What if the product while it’s getting updated, is hooked off the network?
    2. What if an update file is corrupted?
    3. What if an update file is infected with virus?
    4. What if an update file for a specific platform is fed to another platform?
    5. What if your reboot the computers while it’s updated?
    6. What if the server is reset while a client is updating?
    7. What if an application on a client interrupts the update?
    8. What if an upgrade fails? What more problems could be hidden with it?
    9. What if an auto update and a manual update is attempted in parallel?
    10. What if software is attempted to uninstall when an update to it is happening?
    11. What if more than one method of upgrade is initiated from the same client with different instances of the application?
    12. What if there is an upgrade of the platform happening while the product update occurs?
    13. What if the resources required for the upgrade platform are squeezed?
    14. What if the update file has wrong information in it?
    15. What if the file date is changed to a date than the current version yet it has the latest update?

  2. Pingback: Important set of test cases for Login Page | Abode QA

  3. Pingback: Test Cases for Elevator(Lift) | Abode QA

  4. Pingback: Download free software testing books written by India’s most popular tester and mentor | Abode QA

  5. Pingback: Mac Beginner’s tutorial | Abode QA

  6. Pingback: Important set of test cases for Login Page - Abode QA

  7. Pingback: Test Cases for Elevator(Lift) - Abode QA

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: