Name: TestJS Summit 2022
Start: 2022-11-03T15:00:00.000Z
End: 2022-11-04T20:00:00.000Z

 Vinicios Neves

Lera

David Pugh

Károly Török

Joanna Otmianowska

David Barry

Nikolay Advolodkin

Charles

Mykhaylo Ryechkin

Ricardo Machado

Alex Hayton

Robert

Ian Sutherland

Michal Štrajt

Gary Forster

Myron Davis

Creatopy Tech

Vitor Barbosa

Hannah Vivian Shaw

Denis Radin

Luca Fregoso

Pratik Ghosalkar

Rishi Narang

Davide

VyvIT

Antwan Sherif

Ana Spiti

xingwang

Joachim Justh

Varun

Michael Chiche

GERARD

Andy Mthembu

Las pruebas son difíciles, las pruebas requieren tiempo para aprender y escribir, y el tiempo es dinero. Como desarrolladores queremos probar. Sabemos que deberíamos pero no tenemos tiempo. Entonces, ¿cómo podemos conseguir que más desarrolladores hagan pruebas? Podemos crear mejores herramientas.Permíteme presentarte a Playwright - Pruebas confiables de extremo a extremo en diferentes navegadores para aplicaciones web modernas, por Microsoft y completamente de código abierto. El codegen de Playwright genera pruebas para ti en JavaScript, TypeScript, Dot Net, Java o Python. Ahora realmente no tienes excusas. Es hora de jugar tus pruebas correctamente.

Pruebas de Aplicaciones Web con Playwright

Testing web applications with Playwright, a reliable end-to-end testing tool. Playwright offers fast execution, powerful tooling, and support for multiple languages. It provides precise selectors, web-first assertions, and code generation for easy testing. Playwright also offers features like live debugging, tracing, and running tests on CI. The future of Playwright aims to make testing easy and fun, with a focus on creating frustration-free web experiences.

Testing is hard, testing takes time to learn and to write, and time is money. As developers we want to test. We know we should but we don't have time. So how can we get more developers to do testing? We can create better tools.Let me introduce you to Playwright - Reliable end-to-end cross browser testing for modern web apps, by Microsoft and fully open source. Playwright's codegen generates tests for you in JavaScript, TypeScript, Dot Net, Java or Python. Now you really have no excuses. It's time to play your tests wright.

Testing Web Applications with Playwright

Debbie O'Brien

Cypress ha tomado al mundo por sorpresa al traer una herramienta fácil de usar para pruebas de extremo a extremo. Sus capacidades han demostrado ser útiles para crear pruebas estables para aplicaciones de frontend. Pero las pruebas de extremo a extremo son solo una pequeña parte de los esfuerzos de prueba. ¿Qué pasa con tu API? ¿Qué pasa con tus componentes? Bueno, en mi charla me gustaría mostrarte cómo podemos comenzar con pruebas de extremo a extremo, profundizar con pruebas de componentes y luego subir a probar nuestra API, circ

Pruebas de ciclo completo con Cypress

Cypress is a powerful tool for end-to-end testing and API testing. It provides instant feedback on test errors and allows tests to be run inside the browser. Cypress enables testing at both the application and network layers, making it easier to reach different edge cases. With features like AppActions and component testing, Cypress allows for comprehensive testing of individual components and the entire application. Join the workshops to learn more about full circle testing with Cypress.

Cypress has taken the world by storm by brining an easy to use tool for end to end testing. It’s capabilities have proven to be be useful for creating stable tests for frontend applications. But end to end testing is just a small part of testing efforts. What about your API? What about your components? Well, in my talk I would like to show you how we can start with end-to-end tests, go deeper with component testing and then move up to testing our API, circ

Full-Circle Testing With Cypress

Filip Hric

Sí, las cosas grandes vienen en paquetes pequeños. Por ejemplo, ¿no es fantástica la velocidad, retroalimentación y confiabilidad de una prueba unitaria? ¿Sabías que también podemos obtener retroalimentación rápida, enfocada y confiable de nuestras pruebas funcionales de extremo a extremo? Las pruebas atómicas de extremo a extremo son aquellas que son específicas y enfocadas. Son pequeñas en tamaño pero tienen un gran impacto. Este tutorial te enseñará cómo crear pruebas atómicas de extremo a extremo con varios ejemplos de código. Primero, utilizaremos Cypress.io para autenticarnos mediante la configuración de una cookie en lugar de utilizar una interfaz de usuario. Segundo, utilizaremos Cypress.io para establecer un JSON Web Token para la autenticación. Únete a mí y escribamos pruebas pequeñas para obtener grandes resultados.

Pruebas pequeñas, grandes resultados

Automated atomic tests are a great way to improve UI tests by making them less brittle and faster. The tests focus on testing a single feature or component and have minimal UI interactions. The Talk explores examples of automated atomic tests and their implementation on web applications. It also discusses the analysis of atomic tests, login tests, and working with JSON Web Tokens for authentication and authorization. The Talk concludes by highlighting the use of UI and web requests in automated atomic testing.

Yes, Big things do come in small packages. For example, isn’t a unit test’s speed, feedback, and reliability fantastic? Did you know we can also have fast, focused, and reliable feedback from our functional e2e tests? Atomic e2e tests are those that are targeted and focused. They’re tiny in size but large in their impact. This tutorial will teach you how to create atomic e2e tests with several code examples. First, we will use Cypress.io to authenticate by setting a cookie. Instead of using a UI. Second, we will use Cypress.io to set a JSON Web Token for authentication. Join me, and let’s write tiny tests for large results.

Tiny Tests, Large Results

Enviamos correos electrónicos a nuestros usuarios - verificación de cuenta y boletines informativos. Permitimos que el usuario nos contacte enviando un correo electrónico a través de un formulario incorporado. ¿Lo hacemos? ¿Recibe el usuario un correo electrónico de verificación de cuenta o exactamente la notificación para la que se inscribió? Podemos cubrir esta funcionalidad como parte de las pruebas E2E: obtener un correo electrónico y abrirlo para verificar qué contiene. Necesitaremos Playwright y un servidor SMTP falso para capturar los correos electrónicos enviados por la aplicación.

Prueba del Servicio de Correo con Playwright

This Talk discusses how to test mail service with Playwright, covering e-mail verification, reset password user journey, and more. It explores the use of third-party providers for reliable e-mail delivery and demonstrates how Playwright can help perform checks on e-mail content. The Talk also introduces the concept of a fake SMTP server and showcases how fixtures can be used to access the SMTP server and perform assertions on the HTML body of emails. Playwright's HTML rendering feature allows for interaction with email content as if it were a regular web page. It highlights the ability to render HTML from API calls, perform assertions on the rendered page, and exclude dynamically generated data from visual regression tests.

We send emails to our users - account verification and newsletters. We allow the user to contact us by sending an email via inbuild form. Do we? Does the user receive an account verification email or exactly what notification they signed up for? We can cover this functionality as part of E2E tests: get an email and open it to check what is in it. We will need Playwright and a fake SMTP server to capture emails sent by the app.

Testing Mail Service With Playwright

Kat Kmiotek

Repasaremos brevemente qué es Web3 y la arquitectura de una aplicación web3. Luego hablaremos sobre cómo realizar pruebas de extremo a extremo, sus desafíos, algunas herramientas de prueba que están disponibles y una demostración usando cypress y metamask.Agenda: ¿Qué es Web3?; La Arquitectura de una Aplicación Web3; Introducción a las Pruebas E2E Web3; Desafíos de las Pruebas E2E Web3; Herramientas de Pruebas E2E; Demostración.

Pruebas E2E para Aplicaciones Web3

In this Talk, Rafaela discusses Web3, its decentralized and token-based model, and the architecture based on smart contracts. Testing Web3 poses challenges due to the need for third-party providers like MetaMask. Approaches such as mocking the Web3 flow and using end-to-end testing tools like Taskafar are suggested. The trade-offs in Web3 testing include test speed and dependency on third-party apps. Balancing unit, integration, and end-to-end tasks is crucial for a robust testing strategy.

We will go through a brief explanation of what is Web3 and the architecture of a web3 application. Then we will talk about how to end-to-end test, its challenges, some test tools that are available, and a demo using cypress and metamask.Agenda: What is Web3; The Architecture of a Web3 Application; Web3 E2E Tests Introduction; Web3 E2E Tests Challenges; E2E Test Tools; Demo.

E2E Tests for Web3 Applications

Rafaela Azevedo

Los servicios Dockerizados son una excelente herramienta para crear entornos aislados y repetibles ideales para pruebas de integración. En esta sesión, veremos las bibliotecas de Testcontainers que proporcionan una API flexible e intuitiva para controlar programáticamente el ciclo de vida de las dependencias de su servicio en contenedores Docker. Ejecutar bases de datos, Kafka, Elasticsearch e incluso tecnologías en la nube, directamente desde su código de prueba asegura que la configuración del entorno siempre esté actualizada y sea consistente durante el desarrollo local y en los pipelines de CI.Aprenderás todo lo necesario para comenzar a agregar pruebas de integración poderosas a tu base de código sin el dolor de cabeza de administrar dependencias de servicio externas manualmente!

Pruebas de integración encantadoras con Testcontainers

Testing is crucial for development and production, with integration tests becoming more popular. Test containers is a library that integrates with Docker to create reliable test environments. It is flexible and can be used with various frameworks and test libraries. The IDE setup involves configuring the container and connecting it to the application. Test containers can be used for complex operations and allows running tests with real dependencies.

Dockerized services are an excellent tool for creating repeatable, isolated environments ideal for integration tests. In this session, we'll look at the Testcontainers libraries which provide flexible and intuitive API for programmatically controlling lifecycle of your service dependencies in Docker containers. Running databases, Kafka, Elasticsearch, and even cloud technologies, straight from your test code ensures environment config is always up-to-date and consistent during local development and in CI pipelines.You’ll learn everything necessary to start adding powerful integration tests to your codebase without the headache of managing external service dependencies manually!

Delightful Integration Tests With Testcontainers

Oleg Šelajev

Garantizar que tu aplicación no se rompa mientras envías constantemente nuevas características es difícil. Obviamente, con una aplicación o sitio en constante crecimiento, no puedes probar todo manualmente todo el tiempo.La automatización de pruebas y el monitoreo son cruciales para evitar enviar aplicaciones y sitios rotos. Pero, ¿qué funcionalidad debes probar? ¿Cuándo debes ejecutar tus pruebas? ¿Y no son las suites de pruebas complejas muy lentas?En esta sesión, pondremos manos a la obra con Playwright, el marco de pruebas de extremo a extremo, y aprenderemos cómo automatizar navegadores sin cabeza para asegurarnos de enviar nuevas características con confianza.

¿Playwright puede hacer esto?

Playwright is a powerful tool for end-to-end testing, offering support for all major browsers and platforms. It provides features like parallelization, built-in waiting, and assertions. Playwright allows for running tests on multiple browsers with a single command and has functionality for generating tests and performing visual regression testing. It also enables the manipulation of the network layer and loading internals of web pages. Best practices include using short and idempotent scripts, splitting user account flows into separate tests, and cleaning up after each test case.

Guaranteeing that your application doesn't break while constantly shipping new features is tough. Obviously, with a continually growing app or site, you can't test everything manually all the time!Test automation and monitoring are crucial to avoiding shipping broken apps and sites. But what functionality should you test? When should you run your tests? And aren't complex test suites super slow?In this session, we'll get our hands on Playwright, the end-to-end testing framework, and learn how to automate headless browsers to ensure that you confidently ship new features.

Playwright Can Do This?

 Stefan Judis

Overtesting es un problema común con las suites de pruebas unitarias. Es cuando tienes demasiadas pruebas que se rompen con frecuencia y requieren mucho tiempo para mantenerlas en verde. Aquí tienes una nueva perspectiva sobre por qué ocurre esto y cómo puedes evitarlo.

Overtesting: por qué ocurre y cómo evitarlo

This talk is about overtesting, a technique to improve test suites and testing proficiency. It addresses the common problem of spending excessive time on maintaining test suites. The goal is to maintain 100% coverage while spending equal or less time on test suites. The talk suggests splitting tests into functional units, using expect object containing for manageable expectations, and prioritizing ease of testing and time spent.

Overtesting is a common problem with unit test suites. It's when you have too many tests that break often and take up a large amount of time to keep green. Here's a fresh perspective on why that happens and how you can avoid it.

Overtesting: why it happens and how to avoid it

Daniel Irvine

La web ha evolucionado. Finalmente, también lo ha hecho el testing. Cypress es una herramienta de testing moderna que responde a las necesidades de testing de las aplicaciones web modernas. Ha ganado mucha popularidad en los últimos años, obteniendo reconocimiento a nivel mundial. Si has estado esperando aprender Cypress, ¡no esperes más! Filip Hric te guiará a través de los primeros pasos sobre cómo empezar a usar Cypress y configurar tu propio proyecto. La buena noticia es que aprender Cypress es increíblemente fácil. Escribirás tu primer test en poco tiempo y luego descubrirás cómo escribir un test de extremo a extremo completo para una aplicación web moderna. Aprenderás conceptos fundamentales como la capacidad de reintentar. Descubre cómo trabajar e interactuar con tu aplicación y aprende cómo combinar pruebas de API y de UI. A lo largo de todo este masterclass, escribiremos código y realizaremos ejercicios prácticos. Saldrás con una experiencia práctica que podrás aplicar a tu propio proyecto.

Cómo empezar con Cypress

The workshop is led by Filip Nits, a QA lead in Slido, who teaches testers about web development and developers about testing. The workshop focuses on using Cypress for end-to-end testing of the Trello app, covering topics such as installation, writing tests, automating Trello board and element selection, using plugins, and testing cart creation and deletion. It also explores concepts like chaining commands, writing assertions with Chai, sending HTTP requests, intercepting requests, and combining UI and API tests. The workshop provides practical challenges and encourages participants to code along.

The web has evolved. Finally, testing has also. Cypress is a modern testing tool that answers the testing needs of modern web applications. It has been gaining a lot of traction in the last couple of years, gaining worldwide popularity. If you have been waiting to learn Cypress, wait no more! Filip Hric will guide you through the first steps on how to start using Cypress and set up a project on your own. The good news is, learning Cypress is incredibly easy. You'll write your first test in no time, and then you'll discover how to write a full end-to-end test for a modern web application. You'll learn the core concepts like retry-ability. Discover how to work and interact with your application and learn how to combine API and UI tests. Throughout this whole workshop, we will write code and do practical exercises. You will leave with a hands-on experience that you can translate to your own project.

How to Start With Cypress

Las arquitecturas distribuidas modernas son más complejas que nunca, con la mayoría de las empresas operando en múltiples lenguajes, protocolos y estilos arquitectónicos. Esto plantea desafíos significativos para los equipos de ingeniería que cada vez más se les pide entregar más rápidamente. Si bien la práctica de las pruebas de contrato se hizo prominente durante el auge de los microservicios RESTful para abordar desafíos similares, la declaración del problema ha evolucionado. En esta charla, discutiremos estos nuevos desafíos y demostraremos cómo las pruebas de contrato siguen siendo tan relevantes como siempre para ayudar a resolverlos.

Más allá de REST - Pruebas de contrato en la era de gRPC, Kafka y GraphQL

This talk explores the challenges of API communication in a multi-protocol environment and the limitations of REST. It discusses how contract testing can address these challenges by focusing on API communications and reducing reliance on end-to-end tests. The talk also examines the limitations of specifications like OpenAPI and JSON schema and the challenges of endpoint evolution and versioning. It highlights the benefits of consumer-driven contract testing in ensuring API compatibility and provides an overview of the PACT framework as a standardized solution. 

Modern distributed architectures are more complex than ever before, with a majority of companies operating multiple languages, protocols and architectural styles. This poses significant challenges for engineering teams increasingly asked to deliver more at speed. Whilst the practice of contract testing rose to prominence during the RESTful microservices boom to address similar challenges, the problem statement has evolved. In this talk, we'll discuss these new challenges and demonstrate how contract testing is still as relevant as it has ever been in helping to solve them.

Beyond Rest - Contract Testing in the Age of gRPC, Kafka and GraphQL

Matt Fellows

Aprende sobre las razones más comunes de la complejidad en las pruebas, cómo se manifiesta y cómo lidiar con esa complejidad para producir pruebas elegantes incluso para los sistemas más complejos.

Desglosando la complejidad en las pruebas

Today's Talk discusses complexity in tests and how to effectively deal with it. The speaker emphasizes the importance of testing critical user-facing paths and modeling tests from the user's perspective. They also highlight the significance of creating a testing setup that allows any test to run smoothly and the implicit testability of a well-designed system. The Talk explores the impact of choosing the right testing environment, the role of testing setup in mitigating complexity, and the importance of test structure and expectations. The speaker provides practical tips for tackling complexity in tests, such as keeping tests flat, using helper utilities, and splitting tests into separate files.

Learn about the most common reasons for complexity in tests, how it manifests, and how to deal with that complexity to produce elegant tests even for the most complex systems.

Dissecting Complexity in Tests

Artem Zakharchenko

La primera parte de la charla se centrará en una variedad de patrones al usar las pruebas de componentes de Cypress y TDD para crear componentes de React. Los ejemplos de código serán del Tour of Heroes de Angular para que el contenido sea relevante para una comunidad más amplia. Actualmente estoy trabajando en un GitBook reescribiéndolo en React usando pruebas de componentes de Cypress, debería haber mucho contenido para destilar en la charla.La segunda parte de la charla se centrará en estrategias de prueba, tipos de pruebas y dónde aplicarlas, y finalmente compararlas y contrastarlas con los enfoques familiares de la industria.Terminaremos con las conclusiones clave, repositorios de aplicaciones de muestra para ayudar con el aprendizaje y estrategias de implementación.

CCTDD: Diseño impulsado por pruebas de componentes Cypress

Cypress component test-driven design can take front-end engineers to the next level by covering TDD examples, component testing, endpoint testing, and recommended best practices. The TDD flow involves starting with failing tests, making them work, and then improving them. Component tests can be written incrementally, using custom wrappers and props. The differences between React Testing Library and Cypress Component Test lie in the API style. Code coverage can be achieved with Cypress component tests, and the Pack.js Cypress Adapter can be used to avoid test duplication between the backend and frontend.

The first part of the talk will focus on a variety of patterns when using Cypress Component Testing and TDD to create React components. The code samples will be from Angular's Tour of Heroes to make the content relatable to a wider community. Currently I am working on a GitBook rewriting it in React using Cypress Component Tests, there should be plenty of content to distill into the talk.The second part of the talk will focus on test strategies, types of testing and where to apply them, and finally compare &amp; contrast them to the familiar industry approaches.We will finish with key takeaways, sample application repos to help with learning, and rollout strategies.

CCTDD: Cypress Component Test Driven Design

Murat K Ozcan

Node.js recientemente lanzó un runner de pruebas experimental. Esta charla explorará la arquitectura y API del runner de pruebas, y mostrará cómo usarlo con otros módulos principales para crear una experiencia de pruebas sin dependencias externas. Esta charla también examinará posibles adiciones futuras al runner de pruebas.

Pruebas sin dependencias con Node.js

Today's Talk is about zero dependency testing with Node.js. The new test runner in Node.js supports CLI and standalone file execution, and different test runner styles are supported. Writing tests with Node.js is simple using its assert and test modules. The test runner passed one test and failed another, and future work includes implementing a tap parser and adding code coverage and mocking features.

Node.js recently shipped an experimental test runner. This talk will explore the test runner's architecture and API, and show how to use it with other core modules to create a testing experience with no external dependencies. This talk will also look at potential future additions to the test runner.

Zero Dependency Testing With Node.js

Colin Ihrig

En esta charla, quiero presentarte tanto las pruebas de rendimiento frontend como backend y por qué es necesario un popurrí de estas actividades de prueba para asegurarte de que tu sitio web tenga un buen rendimiento. También daré una breve explicación de cómo herramientas como xk6-browser pueden ayudar a ejecutar pruebas tanto a nivel de protocolo (cómo se suelen ejecutar las pruebas de rendimiento a través de interacciones simultáneas en la capa de protocolo) como a nivel de navegador (pruebas con navegadores reales para proporcionar una prueba de rendimiento más realista).Al final de esta charla, deberías estar equipado con nuevos conocimientos sobre las pruebas de rendimiento frontend y backend que puedes aplicar a tus proyectos de trabajo.

Un Popurrí de Pruebas de Rendimiento Frontend y Backend

Performance testing is the practice of measuring and evaluating system response. Front-end and back-end performance testing are crucial for identifying bottlenecks. XK6 Browser is a new tool that allows for browser automation and end-to-end web testing. K6 is a versatile testing tool that covers various use cases. The combination of browser and protocol level testing provides a comprehensive view of performance.

In this talk, I want to introduce you to both frontend and backend performance testing and why a medley of these testing activities are needed to make sure that your website is performant. I'll also give a quick walkthrough as to how tools such as xk6-browser can help with running both protocol-level (how performance testing is normally run through concurrent interactions at the protocol layer) and browser-level tests (testing with real browsers to provide a more realistic performance test).By the end of this talk, you should be equipped with new knowledge regarding frontend and backend performance testing which you can apply to your work projects.

A Medley of Frontend and Backend Performance Testing

Marie Cruz

En este masterclass, cubro no solo lo que WebdriverIO puede hacer, sino también cómo lo utilizarás día a día. He construido los ejercicios en torno a escenarios del mundo real que demuestran cómo realmente configurar las cosas. No es solo "qué hacer", sino específicamente "cómo llegar allí". Cubriremos los fundamentos de las pruebas automatizadas de UI para que puedas escribir pruebas mantenibles y útiles para tu sitio web y/o aplicación web.

Automatización de pruebas utilizando WebdriverIO

This workshop focuses on testing web applications using WebDriverIO, with a demo website called Real World IO. It covers installation, configuration, and running tests using WebDriverIO. The Mocha syntax, debugging techniques, and timeout configuration are discussed. Selectors and their usage, as well as writing tests for the sign-in page and login functionality, are covered. The importance of stable selectors, custom waits, and variable declarations is emphasized.

In this workshop, I cover not only what WebdriverIO can do, but also how you'll be using it day-to-day. I've built the exercises around real-world scenarios that demonstrate how you would actually set things up. It's not just "what to do," but specifically "how to get there." We'll cover the fundamentals of Automated UI testing so you can write maintainable, useful tests for your website and/or web app.

Automated Testing Using WebdriverIO

Kevin Lamping

La charla aborda el escenario actual de la escritura de casos de prueba en JavaScript y los problemas asociados con el tiempo y los recursos que las empresas gastan en escribir los casos de prueba y la falta de automatización en esta área.Luego, la charla cubrirá cómo la inteligencia artificial y el aprendizaje automático se están aprovechando mediante herramientas como Github Copilot y Ponicode para generar automáticamente casos de prueba, simplificando así el proceso de prueba de software.

Pruebas unitarias basadas en aprendizaje automático en JavaScript

This talk explores machine learning-based unit testing in JavaScript and TypeScript, focusing on tools like the Pony Code VS Code extension and GitHub Copilot. The Pony Code tool provides a graphical user interface for generating and managing unit test cases. GitHub Copilot acts as an intelligent code auto-completion tool, understanding the context of the code and suggesting unit test cases. These tools aim to improve code coverage and achieve 100% coverage.

The talk covers the current scenario of writing test cases in JavaScript and the problems associated with the time and resources spent by companies to write the test cases and the lack of automation in this area.Then the talk will cover how AI and machine learning is being leveraged by tools such as Github Copilot and Ponicode to autogenerate test cases thus simplifying the software testing process.

Machine Learning based Unit Tesing in JavaScript

Shivay Lamba

Angular ofrece muchas cosas de serie, incluyendo diversas funcionalidades relacionadas con las pruebas. Esta presentación demostrará cómo podemos aprovechar los sólidos fundamentos de las pruebas unitarias de Angular y aplicar ciertos patrones que facilitan las pruebas. Los temas tratados incluyen: dobles de prueba, patrón de prueba de módulo, arneses, "recetas" sobre cómo probar algunos casos comunes y más.

Pruebas unitarias en aplicaciones Angular

This talk explores unit testing in Angular applications, covering topics such as testing front-end applications, specifics of testing Angular, best practices, and educational resources. It discusses the anatomy of a unit test in both Jasmine and Jest, the setup and initial tests in Angular, testing user interaction and event handlers, testing rendered output and change detection, and unit testing parent components with child components. It also highlights best practices like using test doubles, testing components with dependency injection, and considerations for unit testing. Code coverage is emphasized as a metric that doesn't guarantee bug-free code.

Angular offers many things out of the box, including various testing-related functionalities. This presentation will demonstrate how we can build on Angular's solid unit testing fundamentals and apply certain patterns that make testing easier. Topics covered include: test doubles, testing module pattern, harnesses, "recipes" on how to test some common cases, and more!

Unit Testing Angular Applications

Filip Voska

¿Cuáles son los aspectos que debes tener en cuenta al elegir un marco de automatización? Algunas diferencias principales entre los marcos disponibles.Explica las principales diferencias entre los marcos más conocidos para la automatización: Selenium, Cypress, Playwright y Robot Framework. Aspectos positivos y negativos de los marcos. Dependiendo de las necesidades del proyecto en el que trabajas, ¿cuál es el mejor marco para usar? Breve conversación sobre cómo los marcos se integran con algunas herramientas de gestión de pruebas.

Cómo elegir una herramienta de automatización

I am Lia, a software engineer at Nocare, and I'm going to show you a process to choose an automation tool. I'll compare three frameworks and discuss other integration options. Selenium is a well-established framework with a large community, but it requires third-party integrations for certain types of tests. Cypress is an all-in-one tool that supports unit testing, but it only works with JavaScript and lacks parallel testing capabilities. Playwright is a newer framework that is more complete and supports parallel testing, but it has a smaller community and less mature documentation. If you want a framework that does it all, choose Playwright. Documentation is essential to remember your initial thoughts, show others what is being tested, and establish good practice. Once you have your test list, chosen framework, and prioritizations, schedule a meeting with management. Present your work confidently, as it is the best approach for the team and product.

What are the aspects you should think when choosing an automation framework. Some main differences on available frameworks.Explain the main differences between the most known frameworks for automation: Selenium, Cypress, Playwright and Robot Framework. Positives and negatives about the frameworks. Depending on the needs of the project your work what is the best framework to use. Small talk about how frameworks integrate with some test management tools.

How to Choose an Automation Tool

Lia Moreira

En la charla explicaré los dolores y problemas de la validación de formularios. Luego explicaré el modelo mental de las pruebas unitarias y lo compararé con cómo pensamos en la validación de formularios.Presentaré VEST con un poco de codificación en vivo mostrando su sintaxis de pruebas unitarias.

¿Para qué usar pruebas?!

Today's Talk introduces VEST, a form validation framework that combines the syntax and style of Unitest with form validation. The lack of structure in form validation is a major problem, leading to messy and difficult-to-maintain code. Testing forms and form validation can be challenging, especially with complex logic. VEST offers a solution by allowing the creation of a form validation suite using unit tests. It provides features like multiple validations per field, async validations, and memoization, with support for any JavaScript environment and full TypeScript support.

In the talk I will explain the pains and problems of form validation Then I will explain the mental model of unit tests, and compare it to how we think about form validations.I will introduce vest with a bit of live coding showing its unit testing syntax.

Using Tests for What?!

Evyatar Alush

El desarrollo de software ha cambiado: Despliegues frecuentes, APIs, GraphQL, Arquitectura en la Nube y Automatización CI/CD son la norma. Entonces, ¿por qué las pruebas de seguridad siguen siendo iguales que hace una década? Los equipos líderes se están dando cuenta de que las pruebas de penetración periódicas y las auditorías de seguridad no son suficientes cuando el código se envía a diario. En su lugar, estos equipos están utilizando herramientas centradas en los desarrolladores para ejecutar pruebas de seguridad automatizadas en un pipeline de CI/CD. Únete a Zachary Conger mientras te guía en cómo automatizar las pruebas de seguridad de aplicaciones JS utilizando GitHub Actions.

Automatizar Pruebas de Seguridad de Aplicaciones Web usando GitHub Actions (del equipo de StackHawk)

Welcome to the Test.js and DevSecOps workshops, where we automate web app security testing using Java, React, and StackHawk's DAST utility. We cover setting up GitHub Actions, scanning dependencies with Dependabot, using CodeQL for static analysis, and running StackHawk's DaaST scanner for runtime vulnerability testing. The workshops provide step-by-step instructions for setting up workflows, configuring security testing tools, and reviewing scan results to identify and fix vulnerabilities in the codebase.

Software development has changed - Frequent deployments, APIs, GraphQL, Cloud Architecture and CI/CD Automation are the norm. So why is security testing the same way it was a decade ago? Leading teams are realizing that periodical penetration testing and security audits is not enough when code is being shipped daily. Instead, these teams are using developer-centric tools to run automated security testing in a CI/CD pipeline. Join Zachary Conger as he walks through how to automate application JS security testing using GitHub actions.

Automate WebApp Security Testing using GitHub Actions (from StackHawk team)

Zachary Conger

La pandemia aceleró e introdujo la era de la transformación digital. Todos hemos sido adoctrinados en realizar videollamadas con otros desde prácticamente cualquier dispositivo y ubicación.WebRTC es el centro de este mundo, permitiendo a los usuarios comunicarse directamente entre sí desde la comodidad de sus navegadores y aplicaciones.En esta sesión, Tsahi explica qué es exactamente WebRTC, cómo se diferencia de otras tecnologías web y cómo puedes asegurarte de que tu aplicación WebRTC sea adoptada y utilizada con éxito por tus clientes.

Desafíos de Pruebas y Monitoreo de Aplicaciones WebRTC

WebRTC is an HTML5 specification for real-time media communications between browsers and devices, with challenges in testing and monitoring. Browsers frequently update, potentially breaking WebRTC applications. Testing requires browser automation, consideration of network conditions, and device characteristics. Virtual machines and raw data injection are important for testing. Manual testing is necessary for specific workflows and scalability. Orchestrating multiple machines in the cloud and validating video, packet loss, and bit rate are challenges. Visibility and analysis of WebRTC API calls and metrics are crucial. TestRTC by Spearline offers testing and monitoring solutions.

The pandemic accelerated and ushered in the era of digital transformation. We’ve all been indoctrinated in conducting video calls with others from virtually any device and location.WebRTC is a centerpiece of this world, enabling users to reach out to one another directly from the comforts of their browsers and applications.In this session, Tsahi explains what exactly is WebRTC, how it is different from other web technologies and how you can assure that your WebRTC application gets adopted and successfully used by your clients.

Challenges of Testing and Monitoring WebRTC Applications

Tsahi Levent-Levi

En esta charla, David hablará sobre 5 hábitos que puedes seguir para asegurar la misma calidad que tu código de producción y construir suites de pruebas que sean robustas, consistentes y te ayuden a depurar los problemas rápidamente.- Viaje típico para equipos que adoptan la automatización de pruebas- 5 hábitos a seguir al construir tu suite de pruebas- Nuestros aprendizajes de una actividad reciente de refactorización

5 Hábitos para Tratar tu Código de Pruebas como Código de Producción

Today's Talk focuses on the five habits to treat test code like production code. It emphasizes the importance of modular testing and breaking down UI tests into smaller components. Treating SDETs as software engineers is crucial for code and test quality. The challenges of snapshot testing and the benefits of component testing are also discussed, including improved efficiency and addressing asynchronicity and nested promises.

In this talk, David will talk about 5 habits that you can follow to ensure the same quality as your production code and building test suites that are robust, consistent and help you debug the issues quickly.- Typical journey for teams adopting test automation - 5 habits to follow while building your test suite - Our learnings from a recent refactoring activity

5 Habits to Treat Your Test Code Like Production

David Burns

Las pruebas de seguridad tradicionales para aplicaciones JS se han centrado en el front-end, pero los problemas de seguridad reales suelen estar en la API REST de respaldo. Únete al cofundador de StackHawk, Scott Gerlach, para obtener una breve descripción de por qué debes replantear cómo pruebas tus aplicaciones JS y cómo StackHawk puede ayudarte a encontrar y solucionar rápidamente errores de seguridad.

Pruebas de seguridad automatizadas para aplicaciones JS

At StackHawk, we do application security testing, specifically dynamic application security testing. Legacy DAST tools are not effective for testing JavaScript front ends and APIs. To achieve better testing, it is essential to drive the API directly using industry standards like postman collections, OpenAPI spec, GraphQL, and introspection queries. StackHawk simplifies finding and fixing security issues in applications, integrating with CI/CD processes and providing simple descriptions and examples. Start a free trial at stackhawk.com to improve software quality.

Traditional security testing for JS apps has focused on the front-end, but actual security issues most often lie in the backing REST API. Join StackHawk co-founder Scott Gerlach for a quick overview of why you need to rethink how you test your JS apps and how StackHawk can help you find and fix security bugs fast.

Automated Security Testing for JS Apps

Scott Gerlach

¿Alguna vez te has preguntado cuál es la mejor manera de probar tus utilidades de línea de comandos personalizadas? En esta charla, Florian Rappl te dará algunas ideas sobre lo que puedes hacer para verificar automáticamente tus herramientas CLI y evitar regresiones.- Introducción: ¿Por qué probar las herramientas CLI?- Desafíos: Contaminación del sistema de archivos, problemas de red y base de datos, variables de entorno- Demostración: Mostrar problemas con una herramienta CLI de demostración - Soluciones: Implementación del plan de pruebas, elección del nivel adecuado de contenerización- Demostración: Mostrar la solución utilizando la herramienta CLI anterior- Conclusión

Pruebas de utilidades de línea de comandos

CLI utilities are important to test because they act as an intersection point between different parts of an application. The main challenge in testing CLI utilities is performance, which can be improved by using temporary directories. Managing ports and resources is crucial to avoid conflicts when running multiple test suites. The test context ensures that processes run in the correct context, including the use of the right directories. Running tests on different configurations helps identify compatibility issues and provides comprehensive test coverage.

Ever wondered what is the best way to end-to-end test your custom command line utilities? In this talk Florian Rappl will give you some insights what you can do to automatically verify your CLI tools and avoid regression.- Introduction: Why test CLI tools- Challenges: File system pollution, network and database issues, environment variables- Demo: Showcase issues with a demo CLI tool - Solutions: Test plan implementation, choosing the right level of containerization- Demo: Show solution using the previous CLI tool- Conclusion

Testing CLI Utilities

Florian Rappl

En este masterclass, te presentaré el proyecto migrator.cypress.io de una manera poco convencional, donde además de repasar los comandos de Cypress equivalentes a Protractor (y mostrarte lo simple que es Cypress), también te mostraré cómo probé dicho proyecto evolucionando los scripts de prueba automatizados según la demanda, arquitecturando el conjunto de pruebas de forma evolutiva.

Arquitectura de Pruebas Web y Refactorización con Cypress

The Workshop on Migrator.cyprus.io covered the migration of Protractor test scripts to Cypress using the Migrator.cyprus.io application. The workshop included running tests, discussing project architecture, and code improvements. Custom commands were introduced to reduce code duplication. The workshop also covered guidelines for writing code, version updates, and optimization techniques. Participants shared their experiences and recommendations for using Cypress for UI and API testing.

In this workshop, I will introduce you to the migrator.cypress.io project in an unconventional way, where in addition to going over the Cypress commands equivalent to Protractor (and showing you how Cypress is simpler), I will also introduce you how I tested such a project evolving the automated test scripts on-demand, architecting the test suite in an evolutionary way.

Web Testing Architecture and Refactoring With Cypress

Walmyr

Ready to kickstart your freelance career or just getting started on your journey? You’re in the right spot. Learn from the world’s largest fully distributed workforce in the world.The independent talent movement is the future of work. If you’re considering leaving full-time employment for a career as a freelancer, now is the time to find your successful space in the independent talent workforce. <a href="https://www.flexjobs.com/blog/post/top-freelance-career-fields/">More people are working freelance</a> today than ever before, with the freelance marketplace now contributing $1.2 trillion to the US economy. Some of the most <a href="https://www.flexjobs.com/blog/post/top-freelance-career-fields/">in-demand roles</a> for freelancers right now are senior developers with professional experience in React, Python, Blockchain, QA, and Node.js.This workshop will help you design a sustainable and profitable full-time (or part-time) freelancing/contracting career. We will give you tools, tips, best practices, and help you avoid common pitfalls.At the end of the workshop there will be a Q&amp;A session with a Toptal Talent (Developer) who can answer your questions and provide insights and tips into their own success.

How to Design a Sustainable Freelance/Contracting Career (from Toptal team)

Shane Ketterman

Software development has changed - Frequent deployments, APIs, GraphQL, Cloud Architecture and CI/CD Automation are the norm. So why is security testing the same way it was a decade ago?Leading teams are realizing that periodical penetration testing and security audits is not enough when code is being shipped daily. Instead, these teams are using developer-centric tools to run automated security testing in a CI/CD pipeline. Join Zachary Conger as he walks through how to automate application JS security testing using GitHub.

TestJS Summit is getting back in 2023 in hybrid format with the first in-person day streamed from the Berlin venue including hybrid networking features and interactive entertainment; and second day, as well as the numerous free workshops, streamed to the global audience online.

TestJS Summit is event for QAs and software developers to get up to date with JS testing best practices, sharpen skills and get latest updates from top products core teams. Get a full ticket to participate in workshops, and network with others JS testing folks on December 7-11, 2023.

TestJS Summit 2022

Test JavaScript. Test with JavaScript.