Usability Testing

• Usability means focusing on users
• People use products to be productive
• Users are busy people trying to accomplish tasks
•  Users decide when a product is easy to use

l  To ensure that the product is usable for your user

l  Usability testing should be an iterative practice

l  Completed several times during the design and development life-cycle

l  End result is an improved product and a better understanding of the users that we’re designing for (Kaufmann 2006)

l  Pilot testing

l  Designed to identify hidden issues and eliminate surprises.

l  Pilot testing tests the methods of your actual study as a trial

l  Not with actual users

l  During pilot testing you can make modifications to your final study 

White Box Testing

•          Looking at the internal structure of a program and deriving test cases based on the logic or control flow.

•          Test cases can be designed to reach every branch in the code and to exercise each condition

•          Typically done during unit testing

•          Also known as:

–        Structural Testing

–        Glass-Box Testing

•          Does not address the question of whether or not the program matches the specification

•          Does not tell you if all of the functionality has been implemented

•          Does not discover missing program logic

•          Statement Coverage

•          Decision/Branch Coverage

•          Condition Coverage

•          Decision/Condition Coverage

•          Path Coverage

Black-box Testing

•          Looking at the program from an external point of view and deriving test cases based on the specification.

•          The only criteria upon which the program is judged is if it produces the correct output for a given input.

•          Impossible to write a test case for every possible set of inputs and outputs

•          Some of the code may not be reachable without extraordinary measures

•          Specifications are not always complete

McCabe’s Cyclomatic Complexity

•          Software metric

•          Developed by Tom McCabe (circa 1976)

•          Directly measures the number of linearly independent paths through a program’s source code, taking into account the various decision points

•          Independent of implementation language

Integration Testing

https://drive.google.com/file/d/0BzsuAfabSI9rQjBuVnZXVmRQams/edit?usp=sharing