The post is dedicated to everyone who has virtually not reached our online mitap, which we dedicated to automated testing tools. We publish video from BugsBusters 2020 - watch and there will be a good start to the week.

ITKarma picture

The power of dashboards

Egor Ivanov, Test Automation Specialist (Yandex.Money)

I’ll tell you how and why the integration testing team began to use dashboards. I’ll share what profit we get from this tool and why we consider it important.

0:55 Which specialists will benefit from the report
1:10 What is a dashboard? Life examples. Definition of the term, basic types.
4:05 Introducing the integration testing team. Tool Interaction Diagram: Jira, Autorun, Locker, Pinger, Jenkins
7:32 What to do when something goes wrong - the role of the duty officer
8:15 On-duty dashboard: task scaling, using Grafana
11:26 How metrics are sent. Types of metrics.
13:09 The process of sending metrics from Java and sh
14:10 How to build a dashboard? How can I use dashboards?
15:00 Example 1 - dashboard as a visualizer of metrics
18:20 Example 2 - dashboards as a motivator
22:18 Example 3 - dashboard for analysis
24:45 Example 4 - dashboards to save time
27:00 Summary: what we got from the implementation of dashboards

The Holy Grail of Automation: Can't find it - create it yourself

Andrey Ganin, QA Head (Alfa Bank)

It seems that the choice of tools for automation is huge - exactly until you need E2E tests in C #. I’ll talk about how we created our own framework: the difficulties, unfulfilled hopes and the intricacies of releasing an internal product in open source.

1:30 What will be discussed in the report?
2:20 Background: how Alfa Bank thought about reducing the time it took to check internal products.
3:32 Identification of the main problem - lack of documentation.
4:21 Results of the first implementation of the framework
5:28 Description of the second iteration. SpecFlow. Results of the second implementation
8:32 What if ?. Creating a tool that could accurately and without installing additional software create autotests.
9:20 AFT Desk internal tools interaction diagram
10:58 Why is this all?
13:35 Separation of tests with the framework. How does this happen inside?
16:31 Global change: Microsoft discontinues the development of the Net Framework. Switching to Net Standard
18:20 How the process changed after the transition. Pros and Cons
20:57 Applicability of the framework. Examples. Page Object Patterns
23:11 How to use technology?
24:17 What the new version release looks like in Open Source. Differences with Internal Solution
26:44 Conclusions: why use the framework and who can use it? Development Plans

How we test the Yandex.Tashi widget

Dmitry Sergienko, senior tester (Yandex.Money)
The Yandex.Cash widget is a JS library that works through an iframe. I’ll tell you about my testing experience and our WidgetRunner tool.

0:32 How to test the JS library?
0:54 Yandex.Cash widget: what is it.
2:45 Why we decided to use iframe
3:04 How is this to be tested? The first option (static html-file), its cons.
3:45 About the payment token: what is it and how to get it.
5:01 Why didn't 1 approach work? Following Approaches
6:09 Why is it bad to test only the payment form?
7:48 Test Tool Requirements
8:40 WidgetRunner - how the tool works and its functionality
11:52 Conclusions: what did you get with the implementation of the WidgetRunner tool

P.S. Soon we will open registration on the Android mitap, on which we will touch on the topics of mobile testing. Stay tuned! .