This is a guide to how we would suggest you test Vision Products when you receive an update, there is no definitive right or wrong in how to test, but it is essential that you make sure that operations you use are checked thoroughly before you sign off to go live with the version.

Step-by-step guide

Its a new release of the system so, step 1: 

...

Step 1

1. Obtain the release notes from the wiki site.

2. Have a read through and ask questions on anything you don't understand before you begin testing.

The best way to do this is log a single ticket with all your questions via the Customer Portal.

Once we have answered these questions, step 2:

...

Step 2

1. Plan the testing in stages, the first is to test the new features (we refer to this as an item test). 

   1. Test all the new items shown on the wiki release notes and make sure you have an understanding of how they work.

   2. Test all the improvement items on the wiki release notes, and make a note of the changes you see in them.

2. Report any issues you see in the above items to the Vision Testing Support team, its best to do this in one document or email so that one member of staff can respond to you directly.

Create a support ticket via the Customer Portal for each issue found. This should contain only one item, its really important that you specifically tell us which original item you were testing at the time.

If there is nothing above which is key to you continuing then proceed to step 3: 

...

Step 3

1. Carry out an Operational Test. This tends to be done in stages, team by team so its a little disjointed.

   1. You need to know what you use in the system as you need to test all the functions, the processes, the screens and the reports.

   2. Ensure everything works as expected, what you do here is an ad-hoc test of the functionality that you use.

2. Report any issues found within the stage before continuing.

This usually identifies issues which are not normally noticed when you are testing a single item, at this point you tend to notice more as you are processing using your usual process and its always worthwhile having different users carry out the test as we tend to find no two users do things the same way.

If the operational testing was successful and this is a large release it is worthwhile proceeding with the following step 4:

...

Step 4

1. Full System Test (End to End).

   1. For this stage you need to test from end to end, so its the usual day to day processes that you normally use and you try to do this real time so select a busy hour in the day and reprocess from all teams at the same time to try to emulate as closely as possible to a real live environment.

   2. This should cover all aspects - from receiving to storage to management of the storage to the despatch.

   3. Its important at this point to create new items as well as using existing items,  for example create a new sales order and process it and do the same steps with an existing sales order to make sure they work in the expected manor.

2. Report any issues with this stage to the Vision testing support team, ideally this should be done at least 2 weeks before you plan to go live as this will give us time to resolve the issues, and allow you to recheck them to sign off the "Go Live" one week prior to your actual planned date.

At this point you should not have many issues to report, but what this does identify is issues where the multiuser may need to be looked at such as slowness and delays when processing, the speed of reports.

Issues when Testing

Please Log any issues via the Customer Support Portal 
https://visionsoftware.atlassian.net/servicedesk/customer/portals

If you have not used the Portal before please review Requesting Support for Vision Suite where you will find information on setting up an account and the use of the Portal.

Testing Vision EDI

 If you use Ontech to test your customers files then we will assist with your testing of Vision EDI to ensure that those already tested customers experience no issues with your new version.

...