TEST-DRIVEN DEVELOPMENT WITH JAVA : create higher -quality software by writing tests first with ... solid and hexagonal architecture.

Drive development with automated tests and gain the confidence you need to write high-quality software Key Features Get up and running with common design patterns and TDD best practices Learn to apply the rhythms of TDD - arrange, act, assert and red, green, refactor Understand the challenges of imp...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor principal: MELLOR, ALAN
Formato: Electrónico eBook
Idioma:Inglés
Publicado: [Place of publication not identified] PACKT Publishing Limited, 2023.
Temas:
Java (Computer program language)
Computer software > Development.
Computer software > Testing.
Java (Langage de programmation)
Computer software > Development
Computer software > Testing
Electronic books.
Acceso en línea:Texto completo (Requiere registro previo con correo institucional)
Tabla de Contenidos:
  • Cover
  • Title Page
  • Copyright and Credit
  • Dedicated
  • Contributors
  • Table of Contents
  • Preface
  • Part 1: How We Got to TDD
  • Chapter 1: Building the Case for TDD
  • Writing code badly
  • Understanding why bad code is written
  • Recognizing bad code
  • Bad variable names
  • Bad function, method, and class names
  • Error-prone constructs
  • Coupling and cohesion
  • Decreasing team performance
  • Diminishing business outcomes
  • Summary
  • Questions and answers
  • Further reading
  • Chapter 2: Using TDD to Create Good Code
  • Designing good quality code
  • Say what you mean, mean what you say
  • Take care of the details in private
  • Avoid accidental complexity
  • Revealing design flaws
  • Analyzing the benefits of writing tests before production code
  • Preventing logic flaws
  • Protecting against future defects
  • Documenting our code
  • Summary
  • Questions and answers
  • Further reading
  • Chapter 3: Dispelling Common Myths about TDD
  • Writing tests slows me down
  • Understanding the benefits of slowing down
  • Overcoming objections to tests slowing us down
  • Tests cannot prevent every bug
  • Understanding why people say tests cannot catch every bug
  • Overcoming objections to not catching every bug
  • How do you know the tests are right?
  • Understanding the concerns behind writing broken tests
  • Providing reassurance that we test our tests
  • TDD guarantees good code
  • Understanding problem-inflated expectations
  • Managing your expectations of TDD
  • Our code is too complex to test
  • Understanding the causes of untestable code
  • Reframing the relationship between good design and simple tests
  • Managing legacy code without tests
  • I don't know what to test until I write the code
  • Understanding the difficulty of starting with testing
  • Overcoming the need to write production code first
  • Summary
  • Questions and answers
  • Further reading
  • Part 2: TDD Techniques
  • Chapter 4: Building an Application Using TDD
  • Technical requirements
  • Preparing our development environment
  • Installing the IntelliJ IDE
  • Setting up the Java project and libraries
  • Introducing the Wordz application
  • Describing the rules of Wordz
  • Exploring agile methods
  • Reading user stories
  • the building block of planning
  • Combining agile development with TDD
  • Summary
  • Questions and answers
  • Further reading
  • Chapter 5: Writing Our First Test
  • Technical requirements
  • Starting TDD: Arrange-Act-Assert
  • Defining the test structure
  • Working backward from outcomes
  • Increasing workflow efficiency
  • Defining a good test
  • Applying the FIRST principles
  • Using one assert per test
  • Deciding on the scope of a unit test
  • Catching common errors
  • Asserting exceptions
  • Only testing public methods
  • Preserving encapsulation
  • Learning from our tests
  • A messy Arrange step
  • A messy Act step

Ejemplares similares