We are waiting for you online!
What we will talk about
Cypress for integration testing. What for? How?
Svetlana Goldobina, Raiffeisenbank
About the speaker: Senior tester at Raiffeisenbank, Cash Management team. More than 3 years of experience in test automation in large banks. During her career, she managed to work both with BDD frameworks, including Akita, and take part in its development, and completely switch to the side of testing on the developer stack - JavaScript / TypeScript, Java + Spring.
I believe that testing is not just the generation of cases and the search for bottlenecks, but also a huge scope of work on the study, development, delivery and support.
About the report:Our team wrote tests in BDD style in Russian (Selenium / Selenide + Cucumber + Java). It would seem that it is much easier and more transparent for the team? However, as soon as we lost several QAs, and the developers had to write and modify tests, our tool became a stopper in testing, and BDD did not help here. In this talk, I will tell you how we lowered testing to the bottom and began to restore it.
How we achieved zero errors in the integration tests
Maksim Plavchenok, Bercut
About the speaker: I have been working at Bercut since 2002. He started his career in telecom: he rose from a shift engineer to the head of integration testing. Was a developer, tester, product manager. I love doing what brings problems (and solving them), which is why I came to testing.
About the report: I work for Bercut, I am engaged in integration testing of billing services for telecoms. In September, my team and I passed an important milestone: we received zero errors as a result of integration testing for the release of a new version of billing for a mobile operator. Zero errors means that the customer's business acceptance has not found errors.
It took us 2 years to do this, and this happened due to improvements in several areas: tools, expertise, documentation, work with a customer, a team. Improvements varied in importance: knowing the specifics and processes of the customer is important, moving to a new scale for assessing the complexity of tasks is optional, and working with team motivation is critically important.
All this, as well as what experience I got from this as a head of testing, I will tell in my report.
>>> Let's start the meetup at 18:00 (Moscow time).
Register to receive the link: a letter with the broadcast will be sent to all participants in the mail.
See you online!