October 2024
Intermediate to advanced
270 pages
8h 13m
Spanish
Content preview from 97 cosas que todo programador Java debe saber
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Capítulo 78. Desarrollo basado en pruebas
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
Dave Farley
El desarrollo dirigido por pruebas (TDD) se malinterpreta mucho. Antes de TDD, lo único que ejercía presión para lograr una alta calidad en el software eran los conocimientos, la experiencia y el compromiso de un programador. Después de TDD, había algo más.
En general, se considera que la alta calidad del software incluye las siguientes propiedades del código:
-
Modularidad
-
Acoplamiento flexible
-
Cohesión
-
Buena separación de preocupaciones
-
Ocultación de información
El código comprobable tiene esas propiedades. TDD es desarrollo (diseño) impulsado por pruebas. En TDD, escribimos la prueba antes de escribir el código que hace que la prueba pase. TDD es mucho más que "buenas pruebas unitarias".
Escribir primero la prueba es importante; significa que siempre acabamos con código "comprobable". También significa que la cobertura nunca es un problema. Si escribimos primero la prueba, siempre tendremos una gran cobertura y no tendremos que preocuparnos de ella como métrica, y es una métrica pobre.
TDD amplifica el talento de un programador de software. No hace grandes a los malos programadores, pero hace mejor a cualquier programador.
TDD es muy sencillo-el proceso es Rojo, Verde, Refactorizar:
-
Escribimos ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.