Coverart for item
The Resource Swing extreme testing : the extreme approach to complete Java application testing, Tim Lavers, Lindsay Peters ; reviewers, Prabhakar Chaganti, Valentin Crettaz

Swing extreme testing : the extreme approach to complete Java application testing, Tim Lavers, Lindsay Peters ; reviewers, Prabhakar Chaganti, Valentin Crettaz

Label
Swing extreme testing : the extreme approach to complete Java application testing
Title
Swing extreme testing
Title remainder
the extreme approach to complete Java application testing
Statement of responsibility
Tim Lavers, Lindsay Peters ; reviewers, Prabhakar Chaganti, Valentin Crettaz
Creator
Contributor
Author
Reviewer
Subject
Genre
Language
eng
Summary
Annotation
Member of
Cataloging source
YUS
http://library.link/vocab/creatorName
Lavers, Tim
Dewey number
005.1/4
Illustrations
illustrations
Index
index present
LC call number
QA76.76.T48
LC item number
L38 2008eb
Literary form
non fiction
Nature of contents
dictionaries
http://library.link/vocab/relatedWorkOrContributorName
  • Peters, Lindsay
  • Chaganti, Prabhakar
  • Crettaz, Valentin
Series statement
From technologies to solutions
http://library.link/vocab/subjectName
  • Computer software
  • eXtreme programming
  • Java (Computer program language)
  • COMPUTERS
  • Computer software
  • eXtreme programming
  • Java (Computer program language)
  • Computer software
  • eXtreme programming
  • Java (Computer program language)
Summary expansion
This book is a practical guide based on the authors daily experience developing and maintaining a cutting-edge Artificial Intelligence system. Every chapter comes up with real-life examples and the source code that comes with the book is full of useful (and well-tested) tools. The practical examples make this book suitable learning material for Swing developers. This book is for Swing developers who design and develop complex software for user interfaces that requires extensive testing. If you want to learn to test your Swing GUI components, this book is for you
Label
Swing extreme testing : the extreme approach to complete Java application testing, Tim Lavers, Lindsay Peters ; reviewers, Prabhakar Chaganti, Valentin Crettaz
Instantiates
Publication
Note
  • Title from title screen
  • Includes index
Carrier category
online resource
Carrier category code
  • cr
Carrier MARC source
rdacarrier
Color
other
Content category
text
Content type code
  • txt
Content type MARC source
rdacontent
Contents
  • Cover; Table of Contents; Preface; Chapter 1: What Needs Testing?; An Example; What Classes Do We Test?; Test First-Always!; What Classes Don't We Test?; What Methods Need Testing?; What Methods Don't We Test?; Invoking Hidden Methods and Constructors; Unit Test Coverage; Who Should Implement the Unit Tests?; What About Legacy Code?; Where Does Integration Testing Fit In?; Documentation of Unit Tests; Testing at the Application Level; Who Should Implement the Function Tests?; Automated Test Execution; A Hierarchy of Tests; What Language Should Our Tests Be In?; Is it Really Possible?; Summary
  • Chapter 2: Basics of Unit TestingA Simple Example; The Default Implementation; Test Cases; Design by Contract and Non-Defensive Programming; Test Code Example; Bootstrapping Our Implementation; Load Testing; Summary; Chapter 3: Infrastructure for Testing; Where Should the Unit Tests Go?; Where Should the Function and Load Tests Go?; Management of Test Data; What Do We Require of a Test Data Management System?; Temporary Files; Summary; Chapter 4: Cyborg-a Better Robot; The Design of Cyborg; Using the Keyboard; Mousing Around; Checking the Screen; Summary
  • Chapter 5: Managing and Testing User MessagesSome Problems with Resource Bundles; A Solution; The UserStrings Class; ResourcesTester; How ResourcesTester Works; Getting More from UserStrings; Summary; Chapter 6: Making Classes Testable with Interfaces; The LabWizard Comment Editor; The Wizard; A Test for Wizard; A Test for Step; Handlers in LabWizard; Summary; Chapter 7: Exercising UI Components in Tests; The LabWizard Login Screen; The Design of LoginScreen; UI Wrappers; The Correct Implementation of UILoginScreen; A Handler Implementation for Unit Testing; Setting Up our Tests
  • Our First TestFurther Tests; Some Implicit Tests; Other User Interfaces; Summary; Chapter 8: Showing, Finding, and Reading Swing Components; Setting Up User Interface Components in a Thread-Safe Manner; Finding a Component; Testing Whether a Message is Showing; Searching for Components by Name; Reading the State of a Component; Case Study: Testing Whether an Action Can Be Cancelled; The Official Word on Swing Threading; Summary; Chapter 9: Case Study: Testing a 'Save as' Dialog; The Ikon Do It 'Save as' Dialog; Outline of the Unit Test; UI Helper Methods; Dialogs
  • Getting the Text of a Text FieldFrame Disposal; Unit Test Infrastructure; The UISaveAsDialog Class; The ShowerThread Class; The init() Method; The cleanup() Method; The Unit Tests; The Constructor Test; The wasCancelled() Test; The name() Test; The show() Test; The Data Validation Test; The Usability Test; Summary; Chapter 10: More Techniques for Testing Swing Components; Testing with JColorChooser; Using JFileChooser; Checking that a JFileChooser has been Set Up Correctly; Testing the Appearance of a JComponent; Testing with Frames; Frame Location; Frame Size; Testing with Lists
Control code
324989158
Dimensions
unknown
Extent
1 online resource (vi, 306 pages)
Form of item
online
Isbn
9781847194831
Media category
computer
Media MARC source
rdamedia
Media type code
  • c
Other physical details
illustrations.
http://library.link/vocab/ext/overdrive/overdriveId
cl0500000068
Specific material designation
remote
System control number
(OCoLC)324989158
Label
Swing extreme testing : the extreme approach to complete Java application testing, Tim Lavers, Lindsay Peters ; reviewers, Prabhakar Chaganti, Valentin Crettaz
Publication
Note
  • Title from title screen
  • Includes index
Carrier category
online resource
Carrier category code
  • cr
Carrier MARC source
rdacarrier
Color
other
Content category
text
Content type code
  • txt
Content type MARC source
rdacontent
Contents
  • Cover; Table of Contents; Preface; Chapter 1: What Needs Testing?; An Example; What Classes Do We Test?; Test First-Always!; What Classes Don't We Test?; What Methods Need Testing?; What Methods Don't We Test?; Invoking Hidden Methods and Constructors; Unit Test Coverage; Who Should Implement the Unit Tests?; What About Legacy Code?; Where Does Integration Testing Fit In?; Documentation of Unit Tests; Testing at the Application Level; Who Should Implement the Function Tests?; Automated Test Execution; A Hierarchy of Tests; What Language Should Our Tests Be In?; Is it Really Possible?; Summary
  • Chapter 2: Basics of Unit TestingA Simple Example; The Default Implementation; Test Cases; Design by Contract and Non-Defensive Programming; Test Code Example; Bootstrapping Our Implementation; Load Testing; Summary; Chapter 3: Infrastructure for Testing; Where Should the Unit Tests Go?; Where Should the Function and Load Tests Go?; Management of Test Data; What Do We Require of a Test Data Management System?; Temporary Files; Summary; Chapter 4: Cyborg-a Better Robot; The Design of Cyborg; Using the Keyboard; Mousing Around; Checking the Screen; Summary
  • Chapter 5: Managing and Testing User MessagesSome Problems with Resource Bundles; A Solution; The UserStrings Class; ResourcesTester; How ResourcesTester Works; Getting More from UserStrings; Summary; Chapter 6: Making Classes Testable with Interfaces; The LabWizard Comment Editor; The Wizard; A Test for Wizard; A Test for Step; Handlers in LabWizard; Summary; Chapter 7: Exercising UI Components in Tests; The LabWizard Login Screen; The Design of LoginScreen; UI Wrappers; The Correct Implementation of UILoginScreen; A Handler Implementation for Unit Testing; Setting Up our Tests
  • Our First TestFurther Tests; Some Implicit Tests; Other User Interfaces; Summary; Chapter 8: Showing, Finding, and Reading Swing Components; Setting Up User Interface Components in a Thread-Safe Manner; Finding a Component; Testing Whether a Message is Showing; Searching for Components by Name; Reading the State of a Component; Case Study: Testing Whether an Action Can Be Cancelled; The Official Word on Swing Threading; Summary; Chapter 9: Case Study: Testing a 'Save as' Dialog; The Ikon Do It 'Save as' Dialog; Outline of the Unit Test; UI Helper Methods; Dialogs
  • Getting the Text of a Text FieldFrame Disposal; Unit Test Infrastructure; The UISaveAsDialog Class; The ShowerThread Class; The init() Method; The cleanup() Method; The Unit Tests; The Constructor Test; The wasCancelled() Test; The name() Test; The show() Test; The Data Validation Test; The Usability Test; Summary; Chapter 10: More Techniques for Testing Swing Components; Testing with JColorChooser; Using JFileChooser; Checking that a JFileChooser has been Set Up Correctly; Testing the Appearance of a JComponent; Testing with Frames; Frame Location; Frame Size; Testing with Lists
Control code
324989158
Dimensions
unknown
Extent
1 online resource (vi, 306 pages)
Form of item
online
Isbn
9781847194831
Media category
computer
Media MARC source
rdamedia
Media type code
  • c
Other physical details
illustrations.
http://library.link/vocab/ext/overdrive/overdriveId
cl0500000068
Specific material designation
remote
System control number
(OCoLC)324989158

Library Locations

    • Curtis Laws Wilson LibraryBorrow it
      400 West 14th Street, Rolla, MO, 65409, US
      37.955220 -91.772210
Processing Feedback ...