March 2025
Intermediate to advanced
480 pages
13h 51m
Spanish
Content preview from Estrategias de JavaScript completas
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 21. Pruebas frontales
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
En capítulos anteriores, mencioné que la mejor práctica para escribir cualquier prueba es hacerlo al mismo tiempo que escribes cualquier funcionalidad nueva o haces cualquier refactorización. Las pruebas merecen su propio enfoque, y eso es lo que trataré aquí.
Cuando estés construyendo esta aplicación, debes asegurarte de que no estás liberando regresiones en la funcionalidad existente. Una regresión es cuando un código nuevo provoca involuntariamente errores en la funcionalidad existente en cualquier parte de la aplicación. El equipo de control de calidad, si existe, no tendrá tiempo de realizar pruebas de regresión en cada versión, pero como desarrollador, puedes tomar la iniciativa para asegurarte de que tu código es sólido. Tus pruebas para el nuevo código pueden plantear preguntas sobre cómo funciona algo o qué ocurre cuando no funciona.
En este capítulo trataré:
-
Cómo determinar qué partes del frontend hay que probar
-
Pruebas unitarias
-
Pruebas de extremo a extremo (e2e)
-
Herramientas de comprobación útiles
Los dos objetivos de la escritura de pruebas son evitar que un código roto inesperado acabe delante de los usuarios y documentar la aplicación para que todo el mundo sepa cómo se supone que debe funcionar. Las pruebas también te dan más confianza para futuros desarrollos, porque no te preocupa que tus cambios rompan ...
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.