Information

Testing:

Testing should not be glossed over and conducted presentation style. It's time to get the hands dirty!




Testing

When you turn on your new system you won't want to see bugs helter skelter into the corners. You need to test your system in a structured and cogent fashion. There are four ways in which your system might not act as you'd expect.

Bug #1Bug #2 Bug #3Bug #4 Bug #5Bug #6 Bug #7Bug #8 Bug #9Bug #10 Bug #11

You need careful management over the synchronisation of your test and live environments, as well as strong visibility on your testing so bugs, like these, don't undermine your investment.

Example Testing Application

If you click "Enter" on the form below an example test application will launch in a new window. I wrote this application to control testing via a database engine rather than paper. It allows a user to create a customised testing environment, i.e. it is not set up with one type of IT solution in mind. The program could be used to test a Finance system, an ERP system, a CRM system etc. Addionally, testing areas are set up in the nomenclature of the user.

Users add main testing areas, such as Finance. Dependant test areas, like AR and AP, are then added to these main testing areas. Finally, tests to perform on the new system are added to the dependant test areas, giving a three level structure to the database. Users will then perform the tests adding their notes and the result of the test to the database.

You can use this application for free as long as it is hosted on my server. Send me an email wth your contact details to set your company up. If you want the application installed on your own server an installation charge or licence fee will apply.



  

User Buy In

User Buy In is likely to be the most important element of your implementation. A testing system which is accessible to users can accomplish a number of things


SAP Oracle Sage Coda Microsoft Dynamics
©newITsystem.com 2010, all rights reserved ::

Design: Eriginal