Testing and Quality of Software

1.  Diagnosis
         To reach a high level in tests, it is necessary to understand where you are now. A diagnosis of the current situation will provide a set of recommendations that define the trajectory of success in tests.

2.  Analysis of ambiguity
         It is a technique focused on helping the development of the project requirements and making them clear, unambiguous and testable.

3.  Test Strategy
         Defines the types of tests to run. It is developed based on analysis of project requirements and defines an approach that includes all testing activities.

4.  Test Plan
         A specification that documents the scope, timing, resource allocation and test cycles required to implement the testing strategy.

5.  Management and Monitoring
         It covers the task of monitoring the progress of activities, implementation of communication plan, risk tracking and metric reporting.

6.  Training
         Orientation sessions (Workshop) on the tools used to implement the testing process.

•  Ambiguity Analysis (Requirements)
•  Unit Testing (Code Analysis)
•  Integration Testing
•  System Testing
   -  Facility (Function)
   -  Volume
   -  Load/Stress
   -  Usability
   -  Security
   -  Performance
   -  Storage
   -  Configuration
   -  Compatibility/Conversion
   -  Installability
   -  Reliability
   -  Recovery
   -  Serviceability
   -  Documentation
   -  Procedure
•  User Acceptance Testing (Client)
•  Performance/Load/Stress Testing
•  Regression Testing
•  Metrics & Analysis