Page History

...

1. Section 508 Testing
   • Tools to use – Chrome WAVE plugin, Chrome axe plugin. The Chrome axe plugin is using the same scanning engine as the HHS scanning tool.
   • Section 508 testing need to start as soon as there are pages developed by the dev team
2. Performance Testing
   • Load testing
   • GUI performance (a large volume of data returning per request)
   • REST API performance
3. Security Testing 
   • System team will perform all security scanning
   • QA team need to have a plan to test application security functionalities 
   • Some of this would be static using tools such as Codacy and some Dynamic (Acunetix) and there will be an Audit once we are ready to go into Production later next year.
4. Functional Testing
   • This is the meat of all testing, including GUI, REST API, data loading and data integrity

   • More automation is better, but definitely depends on your load 

5. Usability Testing
   • This is something probably for everyone as GUI is critical the success of the project
6. Availability Testing
   • We would want our system to be Highly Available and Fault Tolerant. So things like instance going down, Container going down, DB going down etc. would need to be covered before we hit Production.

...