Quality Assurance

Software Quality Assurance

Software testing is not an exact science. As code is created, numerous permutations of untried combinations of logic are fitted together in a novel fashion to produce your project's deliverables. All software begins 100% broken and is “coded” towards a state of perfection.
 
As developers “complete” coding on a module, history has taught us that the deliverable is best tested by someone besides the creator. Thus, the role of the software tester, or software quality assurance professional was born. Numerous approaches exist for testing software, and are covered in our training seminars.
 
An effective QA professional is able to articulate the total percentage of code covered in the testing process, and the percentage of estimated bugs still in the product upon release. These calculations are available in our training seminars. 

Software Tester

Software Testing

A professional software tester should be familiar with the following testing techniques:

1. Difference between an Error, and Defect, and a Failure
2. Test Script & Matrix Generation
3. Smoke Testing
4. Unit Testing (White box testing)
5. Integration Testing (Black box testing)
6. UI Testing
7. Data Boundary Testing
8. Load Testing
9. Automated Testing
10. Bug/Ticket Management
11. Test Driven Development (TDD) strategies
12. Determining the amount of code covered in the testing process
13. Determining the amount of defects remaining in the code upon release
14. Determining which development phase produced the majority of defects
15. Determining which development phase requires the most quality practice remediation

Red Rock Research provides software development best practice seminars that cover this material. 

Professionals

Course Guide