ELIRAN SHANI - Automation Lead, HiredScore
INTEGRATING E2E TESTS IN YOUR CI FLOW USING CYPRESS.IO. FROM PREPARATION TO EXECUTION
There are many existing and future challenges when adopting a new automation tool, such as Cypress.io for E2E testing, especially when integrating it as part of the organization's development process. As an automation lead, I have the responsibility of choosing the right tool for the right task and make sure it brings the expected value as the development process improves and grows. In this session, I'll point out the challenges I've faced after more than 10 years in the testing automation area and the solutions that worked for me. I'll talk about the required preparations and dive into the hands-on implementation of Cypress with Jenkins / CircleCI / Github and many more.
ORIT GOLOWINSKI - Senior Product Manager, Gitlab
PROGRESSIVE DELIVERY - TESTING IN PRODUCTION WHILE MINIMIZING RISK
Progressive Delivery is the next stage in Continuous Delivery. We all want to ship faster and in smaller increments and progressive Delivery achieves exactly that with the addition of quick feedback. Having the ability to control the audience that gets the new feature set gives developers ultimate control of exposure and rollback, and allows QA to safely test in production.
ELDAD UZMAN - Senior Automation Engineer, MSD Animal Health Intelligence Technology Labs
LOG MINING, A COMPLEMENTARY STEP FOR TESTING
Software testing is a tough journey in a world of uncertainty, where the testing engineer tries to extrapolate the unknown about his system under test that is forever growing in complexity.
Any tool which can assist this journey should be taken into account.
One such tool is log mining, and although it sounds almost obvious, it has some advantages and of course some pitfalls.
Log mining can assist us with the following tasks:
1. Cross confirmation - especially for load tests:
Load tests are prone to erroneous decision making and collecting data from logs can mitigate this problem
2. Exploring newer and less standardized protocols
Particularly in the realms of IoT and IoE where new protocols emerge to solve various needs, logs can help us track the root cause of test failures more easily.
3. Asynchronous events (observe, calculations, machine learning algorithms)
Tracking and validating asynchronous processing of data can add a lot of insight into your tests.
4. Reproducing system behavior for bug investigation.
Bugs that occurred in the production environment can be reproduced in a dev environment using log mining techniques.
In my lecture, I'll discuss how to log mining helped me with all of these tasks, share my thoughts on how we can build a successful log mining operation, what are the main pitfalls and what kind of professional and interpersonal skills are required to integrate log mining into our testing efforts.
MOSHE AZARIA - QA, Automation and DevOps Team Lead, Sage Intacct
AUTOMATION CULTURE - START WITH THE CUSTOMER (THE DEVELOPER)
Most of the companies use a dedicated team or engineers for automation testing. We've implemented, at Sage Intacct Israel, a culture where the developer is the customer of our infra and CI process, and we make a good product for them!
GIDEON YURY MAKHLIN - QA Team Lead(QA Manager), Fabriik
HOW TO BUILD EFFECTIVE QA TEAM FROM SCRATCH FOR YOUR NEW STARTUP PROJECT
How to choose good people and good technology stack for your QA team.
How to hire motivated professionals, how to build your Automation framework and do not spend all your money before your series A (first) funding round, and to build pretty good and effective test coverage for your project.
DIANA OKS - Automation engineer, Vulcan cyber
TESTING TODAY’S APPLICATION – TEST AUTOMATION TOOLS YOU CAN USE
I would like to talk about the reason I chose to work with a new testing tool instead of writing a new automation framework at my current place of work. I chose to work with Testim.io which is an app that allows you to create UI tests by recording the actions. I've had the opportunity to work as part of a dedicated automation team, part of an R&D scrum, and even as half of the automation team in a start-up. The one thing in common to all of them, that we had to write the framework and the tests as well. Creating the right framework is as important as the tests, sometimes even more because good choices make writing tests easier. While test plans are relevant to the product you work on, the framework need other requirements to take into consideration.
You need to choose the language, what reporter you want to work with, and so on. But you also need to think about the 'who'.
Who is going to maintain this framework? Are the people that responsible for the framework are also responsible for the tests? sometimes they are and sometimes they're not.
After I got my current job I was told that they have this Testim.io tool and it's up to me to decide whether I choose to work with them or choose to write a new framework, but also I should know that they have several tests but not very reliable and basically, everybody ignores them. Since this company, was already two years old by the time I came that meant that there was a lot of work that needed to be done.
RINA SOLOMON - SDET, Last position in Cornerstone
CHALLENGES IN SERVERLESS TESTING
Serverless applications are quickly gaining in complexity —testing is key. And more teams are relying on integration testing a lot more than we may with other architectural styles.
How to isolate such tests from your production cloud accounts, and likely use even more fine-grained accounts than that.
ELI ELIMELECH - Automation Frameworks Architect / Team leader
CODED VS. CODELESS - THE FUTURE OF IN-HOUSE AUTOMATION FRAMEWORKS DEVELOPMENT
With many new codeless tools coming into the market, the question of coded vs. codeless solutions is back.
The answer to this question will radically change the roles within the automation industry.
ABHILASH GIRIDHARAN - Test Automation Architect, UST Global
AI-ENABLED TEST AUTOMATION MAINTENANCE LEVERAGING SELF-HEALING
Test automation teams have scaled many heights in automating enterprise applications at large. However, they run into challenges at execution time when applications undergo updates. A minor revision in the application user interface can result in test failures and become roadblocks for the test automation execution. Changing dynamics of end-user expectations are driving organizations to accelerate code promotion to production. Agile model of development is being endorsed more than ever, thus leading to an absolute requirement to implement measures to reduce test automa-tion maintenance efforts. A self-healing mechanism to auto fix the scripts by identifying errors and triggers would help the testing team minimize maintenance efforts. This also calls for an AI-enabled solution that can learn the nuances of errors to fix them and reduce manual interventions
SARIT VAKRAT - QA&Automation Manager, Amwell
HOW SOFTWARE ARCHITECTURE AFFECTS OUR TESTING
Software architecture has a bigger impact on our QA&Automation efforts, I will walk you through the struggles and how to overcome them. When we are approaching the test design phase and the automation framework design phase; We need to take into account the way the software is built. For example, we will test in a different way a system that is built as a Monolith versus a system that is built as micro-services.
Being a good QA engineer these days is not only to be familiar with the latest trends and tools, but it is also to fully understand how the system is built bottom-up, from the software architecture to how each service interacts and behaves.
DENIS MITIN - Infra Developer, Cybereason
APPROACHES AND METRICS IN AUTOMATING E2E TESTING OF CYBERSECURITY APPLICATION
It is a kind of antivirus with an agent on each machine in the organization. Agent reports all data (processes, users, events, traffic, etc) to the server, analyzes it and decides if the operation was malicious and then reports it to the UI. UI is a kind of inbox, where SOC engineers investigate the received report and perform actions like killing suspicious processes, isolating the PC and so on.
YOAV WEISS - Automation Manager, Imperva
TESTING IN CONTINUES DEPLOYMENT WORLD
Frequent deployment to the production of a complex cyber-security platform is a challenge my team and I learned a lot from. The agility required to push this process even further is a story worth sharing In this lecture I will share from the many experiences and "hard lessons", and how we grew a stable and top-notch automated CI/CD process that allows us to deploy to production with confidence.
Our CI/CD journey is a multiple layered top-bottom journey that consists of what we wanted to accomplish and how we should rebuild our environments, processes, and quality approach.
The journey consists, of rebuilding my team with the right balance of highly skilled “full-stack automation” developers with a quality-first attitude. High focus on early detection and high value to our main inside customers – our developer colleges. Reassess our whole automation strategy and rebuild what is broken while maintaining what works. Continues to retrospect our processes improvement while shifting left to reduce complexity and instability.
Example of a complex and exciting investigation of the scale-longevity issue while demonstrating the great collaboration we have between our teams. We were able to pinpoint the root cause and prevent downtime to our customers. The takeaways are that by persistence and providing of value, we can build better products with higher quality to our customers and that today quality advocates aren’t owned by a single owner but shared by all