On my list of things to do this month is to come up with a set of testing guidelines. Bearing that in mind I came across Anti-clue’s website, who provided the following list of types and levels of testing (the original can be found here). A good starting point to make sure I don’t forget anything!!

• Concept Testing: Testing to see if the concept of the application is viable.
• Functional Testing: Testing if the function that was changed/enhanced works as expected.
• Unit Testing: Testing to see if the program still functions as anticipated based upon scenarios.
• Data Migration Testing: If you are switching to a new system, this is a test to ensure the data from the old system migrates properly to the new system.
• Integrated Testing: Testing to see if the application still functions as anticipated with other applications also based upon scenarios.
• Stress Testing: Testing to ascertain the load an application can withstand.
• Regression Testing: Testing to ensure that with the existing software, the newly added component doesn’t have a negative impact. Normally scenarios are a good idea here.
• Interoperability Testing: Two systems are being tested for the data passed between the systems. Again scenarios are ideal.
• Usability Testing: How users interact with the application. Is it cumbersome or does it flow?
• User acceptance Testing: The overall process satisfaction by the project sponsor and customers.