March 2025
Intermediate to advanced
240 pages
5h 54m
Spanish
Content preview from Eficiente Node.js
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 8. Nodo de Pruebas
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
Probar en el mundo real consiste generalmente en encontrar lo que está mal en algo. Cuando se trata de código, las pruebas consisten en encontrar lo que está bien. Es la garantía de que algo funciona.
El código no probado es simplemente peligroso. El código eficiente y escalable está bien probado. Probar no es sólo asegurarse de que el código hace lo que se supone que debe hacer; también es asegurarse de que el código sigue haciendo lo que se supone que debe hacer después de cualquier cambio en el código, su entorno y sus patrones de uso. Probar consiste en escribir código de alta calidad y detectar posibles problemas lo antes posible.
Probar regularmente el código lo mantiene sano y facilita su mantenimiento. También aumenta la confianza de sus mantenedores para hacer cambios. Hacer cambios en código no probado es una receta para el desastre. Una nueva función del módulo X puede romper otras funciones del módulo Y. No puedes mantener las dependencias en tu cabeza. No puedes probar todo el código manualmente cada vez que hay un cambio. No hay forma de evitarlo. Tienes que escribir código para probar tu código, y sí, tu código de pruebas también puede tener problemas. Las pruebas pueden introducir falsos negativos y falsos positivos. Por eso es sumamente importante hacer bien las pruebas. De eso trata este capítulo.
Aserciones y corredores ...
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.