The art of software testing. Myers (2nd edition) (2004) (811502), страница 39
Текст из файла (страница 39)
See alsoBlack-box testing, Whitebox testingwith Extreme Testing,186–189information required, 92module testing, 92multiple-condition criteria, 51properties of, 52strategy, 90subset definition, 52Test case program, 2Test cases, 17deductive debugging, 166233identifying, 55steps to derive, 66user documentation for, 131Test completion criteria, 148–155Test driver and application, 189Test harness, 190Testing. See also specific test typesof browser compatibility, 198vs. development, 127of Internet applications, 193of large programs, 91psychology of, 5successful vs.
unsuccessful, 7Testing strategies, for Internetapplications, 200Test management, 146Test plan, components of,146–147Test planning and control, 145Three-tier architecture, 196. Seealso Business layer, Dataaccess layer, PresentationlayerTop-down testing, 110–116advantages and disadvantages,114–115vs.
bottom-up testing, 109guidelines, 113Tracking procedures, 147Transactional testing, 208Twelve practices of ExtremeProgramming, 180–181UUnit testing, 91, 183–187test case design, 92234IndexUnit testing (Continued)with JUnit, 188with Extreme Programming,179, 183Usability testing, 135User documentation, formingtest cases with, 131User environment testing, 205User stories, 179VVolume testing, 133WWalkthroughs, 22–24, 38team members, 39Web-based applicationsconfiguration testing with, 138security testing with, 137stress testing with, 134Web browsers:compatibility among,198content delivery, 195Web server, 196White-box testing, 11–13, 44logic coverage testing, 44module test, 92, 204module testing, 92vs.
black-box testing,114XXP. See Extreme Programming(XP)XT. See Extreme Testing (XT).
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
