STAREAST 2022 - Test Automation
Wednesday, April 27
Cypress Advanced Capabilities Declassified for Efficient Cross-Browser Test Automation
PreviewCypress is the fastest growing test automation framework for cross browser testing and it's open source. It has a ton of benefits for developers and test engineers, but also some very advanced and cool capabilities that by knowing them - practitioners could enhance their productivity and test coverage volume. To name a few - interception and network control, visual testing, cloud executions, plugins are a subset of such abilities that organizations need to be familiar with. In this session, Eran Kinsbruner, DevOps Chief Evangelist and best selling author will walk through the top...
.jpg%3Fitok=IVke82tL&sc=3e196208e05441c2daf850505e16fd6f "Iryna Suprun")
Not Your Testing Tool
When we talk about testing and tools we usually mean test automation tools but what if there is more? What if there is a much wider spectrum of tools that can help us to improve quality (and find bugs)? Have you ever thought about secrets your monitoring tool can share? How google screen reader can improve the quality of your app? What is hidden behind those warnings in logs? If not - let’s talk about tools. About not testing tools. I often feel that testers miss a bunch of useful tools that can help to spot issues when not actively testing. These tools can be used by anybody in the team...
Let's Get Serious About Test Automation | Architectural Approach
There are many layers and aspects of software that can and should be tested automatically. Apart from testing software functionality, we can automate testing for performance, accessibility, API layer, visual layer, cross-browser and cross-platform, data, links validation, security, etc. To do all of it and to ensure that the appropriate pieces are tested with the suitable tools, on the proper infrastructure, and at the right time we need an architectural approach.
Automated testing solution is a complex system in itself, so planning, design and development of it should follow the...
Thursday, April 28
Why Salesforce Test Automation Shouldn’t Be Painful
In this talk, Mala will share a holistic view of the challenges of traditional software testing in the complex Salesforce testing ecosystem and provide a roadmap for leaders to overcome implementation roadblocks in partnership with R&D teams. Mala will demonstrate how an investment of a DevOps solution with a Sauce Labs integration helped her agile team achieve time reduction of up to 50% for overall flow, while doubling release velocity without additional headcount. If you are a manager looking to scale end-to-end testing coverage and/or wondering how to make your Salesforce test...
What are your Automation Strategies?
Everyone in your organization has probably discussed automation at least once. But who is responsible for automation? and what are the automation strategies for your organization? Several factors should be considered before jumping into automation. In this session, I will cover what to consider for your automation strategies because it always depends on your organization and what you are trying to achieve.
Attendees in this session will take away : - identify your automation framework - Determine what automation testing infrastructure - Deciding which tests to automate among...
Tri-Layer Testing Architecture
Designing a proper architecture for building your test automation solution is one of the most important knowledge and experience a Test Automation Engineer may possess. The Tri-Layer Testing Architecture gives a good overview on how to design test solutions easily and quickly. About a decade ago people with advanced knowledge were building test automation frameworks with essentially two separate layers: Test Scripts and Test Libraries. The problem with this Bi-Layer architecture is reusability in other applications, specifically the size and complexity of test libraries along with the...
Defining Test Automation Requirements Through Recordings
Most organizations have gone away from the concept of record & playback as their preferred automation method. The early failures of this approach to automation years ago has left significant doubt that this can be used as a primary method of automation. Instead, automation engineers may rely on manual test cases that outline what needs to be done, review a business requirements document, or analyze a design document. Why can’t recordings help not only fill these requirements, but also provide the foundation for automation engineers to work from? The recorders of today are so much...