Scribd
Upload
747 views22 pages

Testing

Software testing is the process of testing software for defects. Manuals are written, reviewed, rewritten, etc. Before they are printed. Tests are the smallest individually executable code units. Usually done by programmers. Test cases might be selected based on code, specification, intuition, etc.

Uploaded by

Naveen Jain
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
747 views22 pages

Testing

Software testing is the process of testing software for defects. Manuals are written, reviewed, rewritten, etc. Before they are printed. Tests are the smallest individually executable code units. Usually done by programmers. Test cases might be selected based on code, specification, intuition, etc.

Uploaded by

Naveen Jain
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 22

Testing User Manual

INTRODUCTION
Testing is the process of testing software for defects. Process of software engineering is testing the software for correct behavior prior to release to end users. Large scale engineering projects follow a more rigorous methodology in order to maximize the number of defects that can be found. For small scale engineering efforts normal testing may be sufficient.
Naveen Jain (1137418147)

Goals of Testing
Detect faults Establish confidence in software Evaluate properties of software Reliability Performance Memory Usage Security Usability
Naveen Jain (1137418147)

Software Testing Difficulties


Most of the software testing literature equates test case selection to software testing but that is just one difficult part. Other difficult issues include: Determining whether or not outputs are correct. Comparing resulting internal states to expected states. Determining whether adequate testing has been done. Determining what you can say about the software when testing is completed. Measuring performance characteristics. Comparing testing strategies.
Naveen Jain (1137418147)

Documentation Effectiveness
Enhances scalabilityImproves usability Lowers customer support costs Improves reliability Increases maintainability

Naveen Jain (1137418147)

Development Stages
Conceptualization and initial design: The writer makes decisions about the scope, target audience, degree of coverage, and general organization of the manual. Preparation: The manual is written, reviewed, rewritten, etc. The manual is in the preparation stage until its content is in final form. Production: The manual is laid out for publication. This might involve typeset ting or making revisions to make the manual look as good as possible when printed by a laser printer or a daisy wheel. Typefaces are chosen, page style (margins, etc.) is designed, final artwork is prepared, and so forth. Publication: The manual is printed or copied and bound, ready for circulation.

Bug Fixing Stage

Naveen Jain (1137418147)

Lifecycle Of Testing

Naveen Jain (1137418147)

Stages of Testing
Testing in the Small Unit Testing Feature Testing Integration Testing

Naveen Jain (1137418147)

Unit Testing
Tests the smallest individually executable code units. Usually done by programmers. Test cases might be selected based on code, specification, intuition, etc. Tools: Test driver/harness Code coverage analyzer Automatic test case generator
Naveen Jain (1137418147)

Integration Testing
Tests interactions between two or more units or components. Usually done by programmers. Emphasizes interfaces.
Issue: In what order are units combined?

Naveen Jain (1137418147)

Stages of Testing
Testing in the Large System Testing End-to-End Testing Operations Readiness Testing Beta Testing Load Testing Stress Testing Performance Testing Reliability Testing Regression Testing
Naveen Jain (1137418147)

Stages Of Testing

Naveen Jain (1137418147)

System Testing

Test the functionality of the entire system. Usually done by professional testers.

Naveen Jain (1137418147)

Risk-based Testing
Risk is the expected loss attributable to the failures caused by faults remaining in the software. Risk is based on Failure likelihood or likelihood of occurrence. Failure consequence. So risk-based testing involves selecting test cases in order to minimize risk by making sure that the most likely inputs and highest consequence ones are selected.
Naveen Jain (1137418147)

Acceptance Testing
The end user runs the system in their environment to evaluate whether the system meets their criteria. The outcome determines whether the customer will accept system. This is often part of a contractual agreement.

Naveen Jain (1137418147)

Regression Testing
Test modified versions of a previously validated system. Usually done by testers. The goal is to assure that changes to the system have not introduced errors (caused the system to regress).

Naveen Jain (1137418147)

Types Of Testing

Manual Testing Automation Testing

Naveen Jain (1137418147)

Manual Testing
Manual Testing is the process of manual testing software for defects. It requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behavior. To ensure completeness of testing, the tester often follows a written test plan that leads them through a set of important test cases.

Naveen Jain (1137418147)

Automation Testing
Test execution: Run large numbers of test cases/suites without human intervention. Test generation: Produce test cases by processing the specification, code, or model. Test management: Log test cases & results; map tests to requirements & functionality; track test progress & completeness

Naveen Jain (1137418147)

Naveen Jain (1137418147)

You might also like