?
Solved

How validating a validated software for a new environment?

Posted on 2011-09-08
1
Medium Priority
?
455 Views
Last Modified: 2013-12-13
Hello,

I've developed an add-in for Microsoft Excel 2007 and validated it by covering all the software requirements by tests, which have been executed, recorded, analysed and documented.

I've made a new version of the add-in for Microsoft Excel 2010, the functionalities are exactly the same (it's the same code), but I've just changed the setup project to create different registry keys during the installation, and the version of the .NET framework used is different (.NET 4 instead of .NET 2).

I'm not sure about what to do for validating this new version of the add-in in a quick but correct manner. As the code has not changed, I think I should not re-test all the software requirements.
I'm thinking about documenting a risk analysis to list the changes between Office 2007 and Office 2010 that could affect the add-in and determine if some functionalities have to be re-tested. Then testing these functionalities (if any) and the new installer (by checking that the add-in and the pre-requisites are correctly installed, and the add-in is correctly loaded in Excel after installation), and make some general testing to verify that the critical functionalities are working.

What do you think about this approach, would you have some comments or advice?

Thanks in advance,
Julien
0
Comment
Question by:JulienVan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 6

Accepted Solution

by:
LeeeRussell earned 2000 total points
ID: 36509013
You could use the method you suggest, but my worry would be that there is no way that you can find out what changes Microsoft has made to the underlying code between the two versions.  You might be able to analyse the functional differences between 2007 and 2010, but you won't know the internals.

Saying that, it still depends on a lot of factors.  If this plugin was a tool that I was releasing within the company I was working at, for internal use only, then I would say that your method was satisfactory.  If you are releasing this to the public as a product, then I would say that you need to re-run your tests.

Fundamentally, this may be the point where you start automating your tests and re-running them is very little effort.
0

Featured Post

[Webinar] How Hackers Steal Your Credentials

Do You Know How Hackers Steal Your Credentials? Join us and Skyport Systems to learn how hackers steal your credentials and why Active Directory must be secure to stop them.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Learn how ViaSat reduced average response times for IT incidents from 10 minutes to 30 seconds.
This article was originally published on Monitis Blog, you can check it here . If you have responsibility for software in production, I bet you’d like to know more about it. I don’t mean that you’d like an extra peek into the bowels of the sourc…
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…

764 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question