how to do regression testing for new upgrade?

[saini]

how to do regression testing for new upgrade?

[Paula Cullen]

Well, your question is quite general so all I can tell you is what we do at my company. We're regulated so we can't just upgrade whenever. We do two upgrades per year basically.

1) We request a temporary instance

2) Clone our production instance on top of it.

3) Upgrade it to the new version

4) Write a test plan and test all of our relevant functionality

5) Clone our prod instance over our test instance

6) Upgrade our test instance to the new version

7) Perform our validation activities through Quality Center

😎 Remediate any issues in our test environment and have the update sets ready to move to prod after upgrade

9) Upgrade our prod instance to the new version

10) Re-perform our test plan

11) Upgrade our dev instance to the new version

Not sure if that helps but I'd be happy to try to answer any more specific questions 🙂

[saini]

I need some basic idea of writing test cases for regression testing to upgrade the servicenow from Geneva to helsinki? any help?

[bomoller]

Hi Saini,

I am more or less in the same situation as you describe, in the process of an upgrade to Helsinki.

We are in the planning phase and have more or less the same considerations as you have, and we have been looking at the Test Management application in ServiceNow.

I can't help you with the specifics on how to write the test cases and test suites. Currently we haven't decided on the abstraction level for the test suites, like one test suite for incident or one test suite for creating incident.

Hope this will help you in some way.

Best Regards,

Bo

[Steve Gibson]

Hello,

As a team currently about to upgrade to Helsinki we have just been through this exact process.

We started using the Test Management application this time, writing a full regression pack to be used moving forward.

- Every OOTB application/function we use has a Test Case written

- Within each Test Case are multiple Tests with detailed steps on what needs to be tested, how and with what users/roles etc.

- Custom applications aren't tested as thoroughly as these are not impacted by upgrades, although we will do tests on functionality such as BR's, UI Actions, Client Scripts etc as part of our overall regression testing.

- For future changes we will update/create new Test Cases to keep our regression pack up to date and accurate to make it easier for testing upgrades.

Exact testing methods are different for everyone but hopefully the above will help.

Instance wise we have 3 (Prod, Test, Dev). We usually do the following;

- Clone Prod to Test

- Upgrade Test

- Regression test and identify defects/changes required

- Clone Prod to Dev

- Upgrade Dev

- Fix and tweak in update sets

- Upgrade Prod

- Pull through update sets and fix/tweak

- Retest

- Clone Dev/Test retrospectively once we are happy in Prod so that we start any new development in Prod like state.