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 66. Programar con GUTs
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
Kevlin Henney
¿Así que estás escribiendo pruebas unitarias? ¡Estupendo! ¿Son buenas? Tomando prestado un término de Alistair Cockburn, ¿tienes GUT? ¿Buenas pruebas unitarias? ¿O has conseguido que alguien (¿tú en el futuro?) acumule deuda técnica en su base de pruebas?
¿Qué quiero decir con bueno? Buena pregunta. Pregunta difícil. Merece una respuesta.
Empecemos por los nombres. Refleja lo que se está probando en el nombre. Sí, no quieres test1, test2, y test3 como esquema de nombres. De hecho, no quieres test en los nombres de tus pruebas: @Test ya lo hace. Dile al lector qué estás probando, no que estás probando.
Ah, no, no me refiero a ponerle el nombre del método que se está probando: dile al lector qué comportamiento, propiedad, capacidad, etc. se está probando. Si tienes un método addItemno querrás una prueba correspondiente en addItemIsOK. Es un olor a prueba muy común. Identifica los casos de comportamiento, y prueba sólo un caso por caso de prueba. Ah, y no, eso no significa addItemSuccess y addItemFailure.
Déjame preguntarte, ¿cuál es el objetivo de tu prueba? ¿Probar que "funciona"? Eso es sólo la mitad de la historia. El mayor reto del código no es determinar si "funciona", sino determinar qué significa "funciona". Tienes ...
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.