The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
Service Desk Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Methodology for testing SP's

Highlighted
Guy Salomon
Regular Collector

Methodology for testing SP's

Does anyone out there know of a check list or outline of the steps for checking your SD system(s) after applying any SP.

Obviously upgrading should always be done on a test system first. But with so many possible pieces to SD it would be nice to have such a document to refer to.

Thanks in advance, Guy
4 REPLIES
Robert S. Falko
Honored Contributor

Re: Methodology for testing SP's

Guy,

I think there are two approaches to testing any software upgrades: 1) check to make sure it does what it claims to do; and 2) check the overall functionality that you need in the software, to make sure it doesn't get broken by the upgrade.

The first is, in a sense, trivial. Here is what we do for the second. Before the software was ever selected, we created use cases to describe exactly what we expected the software to do. These use cases are easily converted directly into a test protocol. After applying any change in a quality assurance environment, we rerun all those test protocols, updating them, where required, when the upgrade changes what we expect of the software.

In short, there can never be a single checklist, because every upgrade will change something different, and every organization will be using the software somewhat differently.

-Josh
Hanspeter Loche
Regular Collector

Re: Methodology for testing SP's

Hi Guy
I do it similar to what Josiah mentioned:
We have some critical business cases. Those cases are documented in an "Acceptance Test Form". After every SP installation we test the behavior of HPOV for every case. The "Acceptance Test Form" will also be updated for new business cases.
We are aware that this cannot be a complete test but our critical business cases are covered.
Cheers
Hanspeter
Mark O'Loughlin
Honored Contributor

Re: Methodology for testing SP's

Hi Guy,

same here. We create users cases based that we have documented and when we upgrade the test system at a minimun we run these tests to ensure things are running as they should.
Note we do update the cases as an ongoing task especially after we make big changes to the live system.

We have certain features that must work as expected and the rules must not be affected in any way.

Be sure to run such tests with accounts that have different roles to ensure things work for all.
Mark O'Loughlin
Honored Contributor

Re: Methodology for testing SP's

Hi,
forgot to mention the tests have to be docmented and signed of before implementing to live. Once the SP is put n live we run the same tests again.

Also if any new functionality is released in the SP we test that to see what it can do for us.
//Add this to "OnDomLoad" event