1. OBJECTIVE QUALITY ASSURANCE TESTS TESTING STRATEGIES
IMPACT OF OBJECT ORIENTATION ON TESTING
TEST CASES
TEST PLAN
CONTINUOUS TESTING
MYER’S DEBUGGING PRINCIPLES

2. QUALITY ASSURANCE TESTS
Why?
Computers are infamous for doing what you tell them to do, not necessarily what you want them to do.
Debugging:
Is the process of finding out where something went wrong and correcting the code to eliminate the errors or bugs that cause unexpected results.
Types of Errors:
Language(syntax) errors
Run – time errors
Logic errors
Categories:
Error – based Testing
Scenario(usage) – based Testing
(contd…)

3. Categories (contd…) Error – based Testing. Scenario – based Testing.
Search for particular clues of interest.
Describe how clues should be tested.
Scenario – based Testing.
Concentrates on what the user does , not on what the product does.
(contd…)

4. TESTING STRATEGIES Testing controlled by many factors risks involved
limitations on resources
deadlines
BLACK BOX TESTING
It is used to represent a system whose inside workings are not available for inspection.
Black box is an imaginary box that hides its internal workings
Test item is treated as “black”, since its logic is unknown; all that is known is what goes in & what comes out, or i/p & o/p
Use: scenario based testing
Eg. User manual

5. …
WHITE BOX TESTING
Specific logic is important and must be tested to guarantee the systems proper functioning.
Use: error based testing
Type : Path Testing-makes certain that each path in a object’s method is executed atleast once during testing
2 types
1. Statement testing coverage – test every statement in the object’s method by executing it atleast once
2. Branch testing coverage – to ensure that every branch alternative has been executed atleast once under some test

6. Detect serious design flaws early in the implementation
TOP – DOWN TESTING
Detect serious design flaws early in the implementation
It supports testing user interface and system integration.
BOTTOM – UP TESTING
It starts with the details of the system and proceeds to higher levels by a progressive aggregation of details until they fit requirements of system.
Leads to integration testing, which leads to system testing
Unit-5, Software Quality & usablity, Dept of CSE, SKPEC, Tiruvannamalai.
5/5/2019

7. IMPACT OF OO ON TESTING Errors.
Less Plausible ( not worth testing for )
More Plausible ( worth testing for now )
New errors might appear

8. … Impact of Inheritance on Testing. Reusability of tests.
Unit-5, Software Quality & usablity, Dept of CSE, SKPEC, Tiruvannamalai.
5/5/2019

9. TEST CASES A test case is a set of What – if questions.
To test a system you must construct some best input cases, that describe how the output will look.
Next, perform the tests and compare the outcome with the expected output.
(contd…)

10. … Testing Good test case Successful test case
Myer’s (objective of testing )
Testing
Is a process of executing a program with the intent of finding errors.
Good test case
That has a high probability of finding an as – yet – undiscovered error.
Successful test case
That detects an as – yet – undiscovered error.
(Contd…)

11. … Guidelines (for developing Quality Assurance test cases)
Describe the feature or service your test attempts to cover
If based on use case, then refer its name.
Specify the feature to test and how to test.
Test the normal use.
Test the abnormal but reasonable use.
Test the abnormal and unreasonable use.
Test the boundary conditions.
While revising document the cases.
Reusability and extendibility should be assessed.
Add Questions that arise out of previous ones.

12. Test Plan
A Test plan is developed to detect and identify potential problems before delivering the software to its users.
A test plan offers a road map.
A dreaded and frequently overlooked activity in software development.
Steps for creating test plan:
Objectives of the test.
Development of a test case
Test analysis.
Regression Testing.
Beta Testing.
Alpha Testing (contd…)

13. … Guidelines (for preparing test plan)
Specify Requirements generated by user.
Specify Schedule and resources.
Determine the testing strategy.
Configuration Control System.
Keep the plan up to date.
At the end of each milestone, fill routine updates.

14. CONTINUOUS TESTING
Testing must take place on continuous basis and this refining cycle must continue throughout the development process until you are satisfied with the results.
During this iterative process, prototypes will be transformed incrementally into the actual application.

15. MYER’S DEBUGGING PRINCIPLES
Bug locating principles.
Think
If you reach an impasse (deadlock), sleep on it.
If the impasse remains, describe the problem to someone else.
Use debugging tools.
Experimentation should be done as a last resort.
Debugging principles.
Where there is one bug , there is likely to be another.
Fix the error, not just the symptom.
The probability of solution being correct drops down as the size increases.
Beware of error correction, it may create new errors.

16. Case Study
Unit-5, Software Quality & usablity, Dept of CSE, SKPEC, Tiruvannamalai.
5/5/2019

17. System Usability- Introduction
The task of satisfying user requirements is basic motivation of quality
Usability testing is different from quality assurance testing in that, rather finding programming defects.
It reflects the users need and satisfaction

18. USABILITY TESTING Definition:
ISO Defines the usability as the effectiveness, efficiency and satisfaction with which a specified set of users to can achieve a specified set of tasks.

19. USABILITY TESTING ISO Definition requires
Defining tasks – What are the tasks
Defining users – who are the users
A means for measuring effectiveness, efficiency and satisfaction – how do we measure usability

20. USABILITY TESTING
Usability measures the ease of use as well as the degree of comfort and satisfaction users have with the software.
Usability is one of the most crucial factor so it should begin in the earlier stage of product development.

21. USABILITY TESTING
Usability test cases begin with the identification of use cases.
When designing test focus on use cases and tasks not features.

22. Jacobson’s Life cycle model
USABILITY TESTING
OOA-
Use case model
Quality assurance
test cases
User satisfaction
Test cases
Usability test cases
Test plan
Jacobson’s Life cycle model

23. Guidelines for Usability testing
The usability testing should involve all software components
Usability need not be more expensive or elaborate
All tests need not involve many subjects
Consider user’s experience as a part of your software usability
Apply usability testing early and often.

24. RECORDING THE USABILITY TEST
When conducting a usability test provide a comfortable environment.
Record the test results using a video camera or a tape recorder.
If possible involve all design team members in observing the test and reviewing the results.

25. USER SATISFACTION TEST
User satisfaction testing is the process of quantifying the usability test with some measurable attributes of the test such as functionality, cost, or ease of use.

26. PRINCIPLE OBJECTIVES
To act as a communication vehicle between users and designers.
To detect and evaluate changes during the design process.
To provide a periodic indication of divergence of opinion about the current design.

27. PRINCIPLE OBJECTIVES (cont…)
To enable pinpointing specific areas of dissatisfaction for remedy.
To provide a clear understanding of just how the completed design is to be evaluated.

28. GUIDELINES FOR DEVELOPING USER SATISFACTI0N TEST
The format of every user satisfaction test is basically the same, but its content is different for each project.

29. A Custom Form For User Satisfaction Test
How do you rate the customer tracking project at this time?
Ease of use
Very Easy
Very Hard
Non Functional
Very Functional
Functionality
Very Expensive
Cost
Very Inexpensive
Intuitive UI
Very Intuitive
Very Hard to Follow
Reliability
Very Reliable
Not Reliable
Comments
I have more to say; I would like to see you