QA Fest 2018. Сергей Король. REACTive automation: how to avoid shooting yourself in the foot

•

1 recomendación•340 vistas

React является одной из самых популярных библиотек для построения пользовательских интерфейсов на текущий момент. Она позволяет создавать закрытые компоненты, умеющие управлять собственным состоянием, а так же - объединять их в более сложные UI блоки. Что же это может означать для автоматизаторов? В рамках предложенной темы будут рассмотрены потенциальные проблемы, с которыми вы можете столкнуться при автоматизации React приложений. Вы увидите практические примеры добавления спец. аттрибутов для закрытых компонентов, познакомитесь с нюансами работы с таблицами и графиками, а также узнаете о способе генерации различного рода событий для сложных UI элементов.

Educación

REACTive AUTOMATION:
HOW TO AVOID SHOOTING
YOURSELF IN THE FOOT?!

QAA Geek and Java fan.
Consultant, speaker and
open-source contributor.
• Lead QAA Engineer
• Consultant: http://sdclabs.com
• GitHub contributor: sskorol
Speaker’s info
• Email: serhii.s.korol@gmail.com
• Twitter: @ss_korol
Contacts
Sergey Korol
Waverley Software
‘‘
2
WHO AM I?

3
State
Component
Virtual DOM
Events
WHAT IS REACT?

4
Real DOM
UI
Server
Old VDOM
New VDOM
DIFF
Data
Store
Render Update
UI events
Server events
Component
WHAT IS REACT?

7
UI
Server
Data
Store
UI events
Server events
WHAT IS REACT?

8
Old VDOM
New VDOM
DIFF
Render
Component
WHAT IS REACT?

9
WHAT IS REACT?
Real DOM
UI
Old VDOM
New VDOM
DIFF
Update

AUTOMATION CHALLENGES
11
• Locators lookup
• Wait context
• Nodes staleness
• Events triggering
• Rendering frequency

14
• Custom attributes
• Events manipulation
PROCESS SIMPLIFICATION

16
Easy elements
lookup
Team
convention
Less
maintenance
Use ReactTestUtils
Avoid 3rd party
components testing

18
Expectation Reality
SORTING & FILTERING

23
Pay attention to types,
formatting and rounding
Always perform root
cause analysis
Use enums to encapsulate
conversion and filtering logic

26
CHARTS TESTING
• Data (including anomalies)
• Business logic
• Visual elements (special cases)

28
Use SVG for
automation
Add custom
attributes
Combine mouse move
and tooltip parsing
Focus on complicated
scenarios

29
CONCLUSION
• Learn your product internals
• Prefer negotiations over
workarounds
• Invest time in learning
programming languages

Más contenido relacionado

La actualidad más candente

Jenkins Pipeline on your Local Box to Reduce Cycle Time

Luca Milanesio

Forcelandia Salesforce CI

Daniel Hoechst

User-percieved performance

Mike North

Top .NET, Java & Web Performance Mistakes - Meetup Jan 2015

Andreas Grabner

Agile android

Godfrey Nolan

London WebPerf Meetup: End-To-End Performance Problems

Andreas Grabner

(R)evolutionize APM

Andreas Grabner

New Server in an Hour

Mike Hillwig

eZ Publish 5: from zero to automated deployment (and no regressions!) in one ...

Gaetano Giunta

Managing changes to eZPublish Database

Gaetano Giunta

It's hard to imagine a modern developer workflow without a sufficiently advanced build system: Make, Gradle, Maven, Rake, and many others. In this talk, we'll discuss the evolution of build systems that leads to distributed build systems. Then, we'll dive into how we can build a scalable system that is fast and resilient, with examples from Google. We'll conclude with the discussion of general challenges of migrating systems from one architecture to another.

Building A Distributed Build System at Google Scale (StrangeLoop 2016)

Aysylu Greenberg

@KileNiklawski with @IpponUSA presents on how we built a job board in one week using JHipster. About JHipster: Our goal is to generate for you a complete and modern Web app, unifying: - A high-performance and robust Java stack on the server side with Spring Boot - A sleek, modern, mobile-first front-end with AngularJS and Bootstrap - A powerful workflow to build your application with Yeoman, Bower, Grunt and Maven

How we built a job board in one week with JHipster

Kile Niklawski

Dev Tools for Admins - Forcelandia 2016

Laura Meerkatz

Applications increasingly talk to each other behind the scenes via APIs. Google’s recent acquisition of Apigee, an API management company, is an indicator of the continued importance of APIs. APIs are like building blocks, providing services and data that can be connected with other APIs to build powerful customized apps. However, developing and testing an API can be challenging because there is no built-in interface, breaking changes can cause widespread outages, sensitive data may be exposed or accessed, and accepted agile testing paradigms can be difficult to adapt to APIs. This session is an introduction to restful APIs and how to test them for security, performance, functionality, and backwards-compatibility risks.

Api fundamentals

AgileDenver

Javantura v4 - CroDuke Indy and the Kingdom of Java Skills - Branko Mihaljevi...

HUJAK - Hrvatska udruga Java korisnika / Croatian Java User Association

The Rounds Project: Growing from thousands to millions - Berry Ventura & Yoah...

DroidConTLV

Vous avez entendu parler des acteurs Akka et vous vous demandez quels types d’architectures vous pouvez mettre en place, ou comment les intégrer dans votre architecture ? Et quelle est la courbe d’apprentissage ? A travers un retour d’expérience, nous répondrons à ces questions et vous montrerons comment en trois mois nous avons mis en place une architecture basée sur Akka et Spray en Scala. Par Nicolas Jozwiak

Supervise your Akka actors

Publicis Sapient Engineering

FishEye and Crucible Presentation

Ellen Feaheny

A major part of our lives is working safely with production - yet few organizations today are designing production to enable higher quality and end to end verification of the code we write and deploy. In this talk, we build on the foundation of great microservice architectures to include the first class design of testability as one of the most important artifacts that high velocity and high-quality teams should consider. In particular, we’ll explore what it’s like to build quality software with no development, QA, or staging environments. We'll include a deep dive into “verification in production” and what it really takes to build software that can safely be tested continuously in production. Let’s build developer happiness by *knowing* production is correct. Given at QCon New York June 2017

Production - Designing for Testability

Michael Bryzek

Getting started with mobile application development

ColdFusionConference

La actualidad más candente (20)

Jenkins Pipeline on your Local Box to Reduce Cycle Time

Forcelandia Salesforce CI

User-percieved performance

Top .NET, Java & Web Performance Mistakes - Meetup Jan 2015

Agile android

London WebPerf Meetup: End-To-End Performance Problems

(R)evolutionize APM

New Server in an Hour

eZ Publish 5: from zero to automated deployment (and no regressions!) in one ...

Managing changes to eZPublish Database

Building A Distributed Build System at Google Scale (StrangeLoop 2016)

How we built a job board in one week with JHipster

Dev Tools for Admins - Forcelandia 2016

Api fundamentals

Javantura v4 - CroDuke Indy and the Kingdom of Java Skills - Branko Mihaljevi...

The Rounds Project: Growing from thousands to millions - Berry Ventura & Yoah...

Supervise your Akka actors

FishEye and Crucible Presentation

Production - Designing for Testability

Getting started with mobile application development

Similar a QA Fest 2018. Сергей Король. REACTive automation: how to avoid shooting yourself in the foot

Voice assistants and chatbots automation

Sergey Korol

Silverlight vs HTML5 - Lessons learned from the real world...

Peter Gfader

With all the buzz about DevOps we tend to believe that everyone is doing it when in fact most companies are not because it’s hard to do in a legacy world. And according to IDC –the vast majority of enterprise apps are on-premise. And even in 2018, only 27.8% of the worldwide enterprise applications market are expected to be SaaS-based compared to 16.6% of the market in 2013. During this talk I will point out the difficulties on achieving DevOps Zen for On-Premise applications, and the way that those in the silent majority can get out off the bench and into the DevOps game.

Legacy On Premise Apps Got You Down? No Problem - DevOps for All

Muly Gottlieb

How to run a global, cloud scale event for 10.000 people

RobBos10

Episode 9 - Building soap integrations in salesforce

Jitendra Zaa

Dev ops lessons learned - Michael Collins

Devopsdays

Episode 16 - Introduction to LWC

Jitendra Zaa

How did a small, completely self-funded team build a web framework that became more popular than comparable tools with million-dollar budgets? By welcoming the outsiders. Mike will recount how Sails.js grew from an internal tool to one of the most popular frameworks for Node.js, without forgetting its roots. Javascript is quickly becoming more than just the lingua franca of the web– it’s rapidly growing in popularity on servers, mobile devices, and embedded systems. In many ways, “Javascript is the new Java.” More and more backend developers are becoming familiar with tools like Bower, Yeoman and Grunt, and Angular has empowered web developers to create single page apps as part of their everyday workflow. As the industry standardizes around Javascript, it’s not only important to take advantage of new tools; we must also make sure these new tools and methodologies are accessible and understandable to developers from more traditional backgrounds. In this talk, Mike will reflect on the experiences he’s had building and managing an open-source Node.js framework, Sails.js. He’ll discuss the success we’ve had attracting interlingual developers to Sails, and share some lessons and difficulties we’ve encountered migrating a new generation of developers from PHP, Java, .NET and Rails to Node.js. He will share examples from both sides of the spectrum, both community-related and technical, including: How to encourage (not dissipate) the growth of subcultures within an open-source community How to reconcile different levels of familiarity and preference for different collaboration tools (Github, IRC, Google Groups, etc) How to assimilate the technical heritages from past frameworks (i.e. syntax, nomenclature, project structure) How to meet expectations around reference documentation, and direct community contribution towards guides and tutorials Mike is an engaging speaker with a knack for dynamic Q&A. He is passionate about the subject matter and can adapt the talk to any time frame. http://allthingsopen.org/talks/rags-to-open-source-the-story-of-sails-js/ http://allthingsopen.org/speakers/mike-mcneil/

Rags to Open Source - AllThingsOpen, Raleigh, NC 2014

Mike McNeil

React Tech Salon

Chenguang ZHANG

JIRA 7 for Developers - Bartek Gatz Filip Rogaczewski Ian Grunert

Atlassian

Micro Service Architecture

Eduards Sizovs

12-factor-jruby

Joe Kutner

SharePoint Saturday San Antonio: Workflow 2013

Sam Larko

What is cool with Domino V10, Proton and Node.JS, and why would I use it in ...

Heiko Voigt

Untangling the web11

Derek Jacoby

Play Framework: Intro & High-Level Overview

Josh Padnick

This is about leveling-up and REVOLUTIONIZING Testing as part of your Agile/DevOps Transformation. You can contribute more than testing functionality. You need to Level-Up your skill set by understanding the apps you are testing. # Images, # JS Files, # SQL Statements, Connection Pool Utilization and Garbage Collection Activity have to be added to your portfolio. Check these metrics when you do your functional testing and report regressions to your engineers even though the functionality is still good. But you just uncovered an Architectural regression that will lead to a scalabilty and performance problem. Finding these problems early will eliminate a lot of wasted and unplanned time later on in the lifecycle. that is your contribution to delivering software faster with better quality

BTD2015 - Your Place In DevTOps is Finding Solutions - Not Just Bugs!

Andreas Grabner

Rails is optimised for the first weeks of development. At the later phases it's no longer the speed of adding new views and data that matters. It's often more about the different (and changing!) ways of using the data. The business logic gets more complicated. DDD has answers to those problems. Detecting the bounded contexts is the crucial skill. Choose which parts of the app leave as CRUD and which could go into more of the tactical DDD.

From Rails legacy to DDD - Pivorak, Lviv

Andrzej Krzywda

Slides from the talk "CI doesn’t start with Jenkins" from DevOps Stage 2018 (12-13 October 2018, Kyiv, Ukraine) CI is not only a tool. You cannot simply install and configure Jenkins or whatever system and say that you have CICD pipeline. Here I'm trying to cover different aspects and dependencies of the CICD process based on Preply Inc experience. External Links: [2] CatOps Telegram channel: https://t.me/catops [2] HashiCorp User Group Kyiv: https://www.meetup.com/Kyiv-HashiCorp-User-Group/ [12-24 ]https://www.endpoint.com/blog/2014/05/02/git-workflows-that-work [49-50]: https://nvie.com/posts/a-successful-git-branching-model/ [51-56]: https://www.toptal.com/software/trunk-based-development-git-flow [64] Django Anonymizer: https://github.com/knowledge-point/dj_anonymizer

CI doesn’t start with Jenkins

Yuriy Rochnyak

Android : How Do I Code Thee?

Viswanath J

Similar a QA Fest 2018. Сергей Король. REACTive automation: how to avoid shooting yourself in the foot (20)

Voice assistants and chatbots automation

Silverlight vs HTML5 - Lessons learned from the real world...

Legacy On Premise Apps Got You Down? No Problem - DevOps for All

How to run a global, cloud scale event for 10.000 people

Episode 9 - Building soap integrations in salesforce

Dev ops lessons learned - Michael Collins

Episode 16 - Introduction to LWC

Rags to Open Source - AllThingsOpen, Raleigh, NC 2014

React Tech Salon

JIRA 7 for Developers - Bartek Gatz Filip Rogaczewski Ian Grunert

Micro Service Architecture

12-factor-jruby

SharePoint Saturday San Antonio: Workflow 2013

What is cool with Domino V10, Proton and Node.JS, and why would I use it in ...

Untangling the web11

Play Framework: Intro & High-Level Overview

BTD2015 - Your Place In DevTOps is Finding Solutions - Not Just Bugs!

From Rails legacy to DDD - Pivorak, Lviv

CI doesn’t start with Jenkins

Android : How Do I Code Thee?

Más de QAFest

QA Fest 2019. Сергій Короленко. Топ веб вразливостей за 40 хвилин

QA Fest 2018. Сергей Король. REACTive automation: how to avoid shooting yourself in the foot

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a QA Fest 2018. Сергей Король. REACTive automation: how to avoid shooting yourself in the foot

Similar a QA Fest 2018. Сергей Король. REACTive automation: how to avoid shooting yourself in the foot (20)

Más de QAFest

Más de QAFest (20)

Último

Último (20)

QA Fest 2018. Сергей Король. REACTive automation: how to avoid shooting yourself in the foot