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

Mostrar otras versiones (1)

"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...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autores principales: Farcic, Viktor (Autor), Garcia, Alex (Computer programmer) (Autor)
Formato: Electrónico eBook
Idioma:Inglés
Publicado: Birmingham ; Mumbai : Packt Publishing, [2015]
Colección:Community experience distilled.
Temas:
Application software > Testing.
Application software > Development.
Java (Computer program language)
Logiciels d'application > Développement.
Java (Langage de programmation)
COMPUTERS > Programming Languages > JavaScript.
Acceso en línea:Texto completo (Requiere registro previo con correo institucional)
Tabla de Contenidos:
  • 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

Ejemplares similares