Test-driven Java development : invoke TDD principles for end-to-end application development with Java /

Test-driven Java development : invoke TDD principles for end-to-end application development with Java /

Saved in:
Bibliographic Details
Author / Creator:Farcic, Viktor, author.
Imprint:Birmingham ; Mumbai : Packt Publishing, [2015]
©2015
Description:1 online resource (258 pages) : illustrations
Language:English
Series:Community experience distilled
Community experience distilled.
Subject:
Application software -- Testing.
Application software -- Development.
Java (Computer program language)
Application software -- Development.
Application software -- Testing.
Java (Computer program language)
Electronic books.
Format: E-Resource Book
URL for this record:http://pi.lib.uchicago.edu/1001/cat/bib/11908386
Hidden Bibliographic Details
Varying Form of Title:Invoke TDD principles for end-to-end application development with Java
Other authors / contributors:Garcia, Alex (Computer programmer), author.
ISBN:9781783987436
178398743X
9781783987429
1783987421
Notes:Includes index.
Print version record.
Summary:"Test-driven development (TDD) is a development approach that relies on a test-first procedure that emphasises writing a test before writing the necessary code, and then refactoring the code to optimize it. The value of performing TDD with Java, one of the most established programming languages, is to improve the productivity of programmers, the maintainability and performance of code, and develop a deeper understanding of the language and how to employ it effectively. Starting with the basics of TDD and reasons why its adoption is beneficial, this book will take you from the first steps of TDD with Java until you are confident enough to embrace the practice in your day-to-day routine. You'll be guided through setting up tools, frameworks, and the environment you need, and will dive right in to hands-on exercises with the goal of mastering one practice, tool, or framework at a time. You'll learn about the Red-Green-Refactor procedure, how to write unit tests, and how to use them as executable documentation. With this book you'll also discover how to design simple and easily maintainable code, work with mocks, utilise behaviour-driven development, refactor old legacy code, and release a half-finished feature to production with feature toggles. You will finish this book with a deep understanding of the test-driven development methodology and the confidence to apply it to application programming with Java"--Provided by publisher.
Other form:Print version: Farcic, Viktor. Test-driven java development. Birmingham ; Mumbai : Packt Publishing, [2015] 9781783987429
Table of Contents:
  • Cover
  • Copyright
  • Credits
  • About the Authors
  • About the Reviewers
  • www.PacktPub.com
  • Table of Contents
  • Preface
  • Chapter 1: Why Should I Care for Test-driven Development?
  • Why TDD?
  • Understanding TDD
  • Red-green-refactor
  • Speed is the key
  • It's not about testing
  • Testing
  • The black-box testing
  • The white-box testing
  • The difference between quality checking and quality assurance
  • Better tests
  • Mocking
  • Executable documentation
  • No debugging
  • Summary
  • Chapter 2 : Tools, Frameworks, and EnvironmentsGit
  • Virtual machines
  • Vagrant
  • Docker
  • Build tools
  • The integrated development environment
  • The IDEA demo project
  • Unit testing frameworks
  • JUnit
  • TestNG
  • Hamcrest and AssertJ
  • Hamcrest
  • AssertJ
  • Code coverage tools
  • JaCoCo
  • Mocking frameworks
  • Mockito
  • EasyMock
  • Extra power for mocks
  • User interface testing
  • Web testing frameworks
  • Selenium
  • Selenide
  • The behavior-driven development
  • JBehave
  • Cucumber
  • Summary
  • Chapter 3 : Red-Green-Refactor
  • from Failure through Success until Perfection Setting up the environment with Gradle and JUnit
  • Setting up Gradle/Java project in IntelliJ IDEA
  • The red-green-refactor process
  • Write a test
  • Run all the tests and confirm that the last one is failing
  • Write the implementation code
  • Run all the tests
  • Refactor
  • Repeat
  • The Tic-Tac-Toe game requirements
  • Developing Tic-Tac-Toe
  • Requirement 1
  • Test
  • Implementation
  • Test
  • Implementation
  • Test
  • Implementation
  • Refactoring
  • Requirement 2Test
  • Implementation
  • Test
  • Implementation
  • Test
  • Requirement 3
  • Test
  • Implementation
  • Test
  • Implementation
  • Refactoring
  • Test
  • Implementation
  • Test
  • Implementation
  • Test
  • Implementation
  • Refactoring
  • Requirement 4
  • Test
  • Implementation
  • Refactoring
  • Code coverage
  • More exercises
  • Summary
  • Chapter 4 : Unit Testing
  • Focusing on What You Do and Not on What Has Been Done
  • Unit testing
  • What is unit testing?
  • Why unit testing?
  • Code refactoring
  • Why not use unit tests exclusively?Unit testing with TDD
  • TestNG
  • The @Test annotation
  • The @BeforeSuite, @BeforeTest, @BeforeGroups, @AfterGroups, @AfterTest, and @AfterSuite annotations
  • The @BeforeClass and @AfterClass annotations
  • The @BeforeMethod and @AfterMethod annotations
  • The @Test(enable = false) annotation argument
  • The @Test(expectedExceptions = SomeClass.class) annotation argument
  • TestNG vs JUnit summary
  • Remote controlled ship requirements
  • Developing the remote-controlled ship
  • Project setup
  • Helper classes

Similar Items