Quality Assurance CS 615

Mission Statement The Quality Assurance team will provide assurance to stakeholders in CS-615/616 projects that their projects meet their requirements for correctness, usability, reliability, and maintainability

General Tasks Establishment of Best Practices Testing for Correctness Load Testing for Server Based Applications Assuring Maintainability Evaluating Usability Tracking of Compliance to All of the Above

Best Practices Guidelines –When applicable, RDBMS databases should be used. Local databases such as MS Access should be avoided (Performance, Reliability) –If a given language makes it optional to force variable declaration, it should be turned on. (Reliability, Maintainability) –Code should be commented before or during typing. (Maintainability)

Guidelines continued –When public classes are created, all public interfaces should be documented separately from internal code documentation. (Maintainability, Usability) –Browser based applications should be compatible with more than one browser (Reliability, Usability) –Any user input should be pre-filtered to prevent database errors (Reliability, Usability) Best Practices

Correctness Testing Step 1: Review of requirements/design documents Step 2: Black box testing –The approach to black box testing depends largely on the application being developed Step 3: White box testing as needed

Technologies Custom software –QA Tracking Website Pre-made software –OpenSTA automated virtual user scripting and load testing for HTTP/HTTPS –Mozilla general purpose web browser used for secondary testing

Purpose - To provide project status tracking for CS 615/616 projects Key Features - Allows administrators and teams to provide status updates on their projects. Prioritization of outstanding materials and errors will be displayed to both types of users Quality Assurance Tracking Website

Purpose – General purpose web browser based on Netscape. Use – Mozilla will be used to test browser based applications for compatibility with more than one browser.  Where to get it-

Purpose - To generate realistic heavy loads simulating the activity of numerous virtual users. Setup - Allows scripts to be created which will test websites over HTTP or HTTPS for performance. Scripts may be coded manually or may be recorded in the Script editor. Use – Once test scripts are created, they may be batched together. Multiple virtual users may then be created to run the tests simultaneously. Results – Results of tests may be exported to comma separated format for analysis in most spreadsheets.  Where to get it?