Download A Practical Guide to Testing Object-Oriented Software by John D. McGregor PDF

By John D. McGregor

A pragmatic advisor to trying out Object-Oriented software program specializes in the real-world concerns that come up in making plans and imposing powerful checking out for object-oriented and component-based software program improvement. It indicates how trying out object-oriented software program differs from trying out procedural software program and highlights the original demanding situations and possibilities inherent in object-oriented software program trying out. The authors display how object-oriented software program improvement permits checking out to be built-in into each one degree of the method - from defining necessities to method integration - leading to a smoother improvement approach and a better finish caliber. As they keep on with this technique, they describe what to check at every one level in addition to provide experienced-based trying out ideas. you can find details on such very important themes as: trying out research and layout versions, together with picking attempt situations to steer layout inspections checking out elements, frameworks, and product strains The checking out demanding situations of inheritance and polymorphism tips to devise an efficient trying out approach trying out sessions, together with developing a try out motive force and try out suites trying out item interactions, masking sampling try circumstances, off-the-shelf parts, protocol checking out, and try styles checking out type hierarchies, that includes subclass try out requisites trying out dispensed items, together with threads, existence cycle checking out, and internet server checking out trying out structures, with info on tension, existence cycle, and function trying out One accomplished instance runs in the course of the booklet to illustrate checking out suggestions for every degree of improvement. moreover, the ebook highlights vital questions that testers may still ask while confronted with particular checking out initiatives. The authors recognize that trying out is frequently seen as an important evil, and that assets allotted to trying out are usually constrained. With that during brain, they current a important repertoire of trying out options from that you may opt for those who suit your finances, time table, and desires.

Show description

Read or Download A Practical Guide to Testing Object-Oriented Software PDF

Similar object-oriented software design books

Objects First with Java: A Practical Introduction Using BlueJ

BlueJ is a Java improvement setting that runs on most sensible of the sunlight Microsystems Java improvement equipment employing the traditional compiler and digital computer. It permits readers to create items of any type and engage with their tools. For the 1st time, the usually tricky innovations of items and periods are introduced alive in an simply manipulable visible shape.

EJB Design Patterns: Advanced Patterns, Processes, and Idioms

Truthfully, the ebook isn't a nasty e-book, it offers an attractive but demanding subject, find out how to layout EJB (or in a broader feel, J2EE program) utilizing layout styles. in spite of the fact that, this booklet has a wide intersection with middle J2EE styles, which not just comprises extra styles (on all layers), but in addition is written in a extra transparent and complete means.

Object-oriented and Classical Software Engineering

This publication specified the several tools of attacking software program layout and introduces UML diagrams, statecharts, and association. an excellent ebook if you should be operating within the box facing the constitution and strategies that actual company' use for software program layout.

Additional info for A Practical Guide to Testing Object-Oriented Software

Example text

Some of the preconditions for operators are implicit in the state diagram, while state definitions are implicit in the OCL specification. For example, within the context of the state diagram, the get() operation is permitted only when a puck supply object is in a Not Empty state since no transition from the Empty state is labeled with a get() event. This precondition is expressed in the OCL specification as a constraint on the count attribute associated with a PuckSupply, with no mention of a Not Empty state.

Development and testing processes are distinct primarily because they have different goals and different measures of success. Development strives to build a product that meets a need. Testing strives to answer questions about the product, including whether the product meets the need that it is intended to meet. Consider, for example, the number of defects identified after testing some developed software. The lower the defect rate (ratio of test cases that fail to the total number used), the more successful the development is considered to be.

Some of the preconditions for operators are implicit in the state diagram, while state definitions are implicit in the OCL specification. For example, within the context of the state diagram, the get() operation is permitted only when a puck supply object is in a Not Empty state since no transition from the Empty state is labeled with a get() event. This precondition is expressed in the OCL specification as a constraint on the count attribute associated with a PuckSupply, with no mention of a Not Empty state.

Download PDF sample

Rated 4.09 of 5 – based on 24 votes

About the Author

admin