Семенченко Антон Владимирович
IT Consultant - COMAQA
Minsk, Belarus

IT консультант. Старший преподаватель БГУ, ФПМИ, каф. Технологий программирования. Основатель сообществ QA специалистов COMAQA.by, суровых разработчиков на С / С++ COREHARD.by, сообщества IT специалистов, переехавших в Беларусь InterIT.by. Более 20 лет в IT, основная специализация: автоматизированное тестирование, низкоуровневая разработка на C++ и ниже, менеджмент, тренинги.

Talks (17)
  • 28.03.2022
    An analyst's work in implementing zero code, low code, no code and DSL in examples

    Let's talk about the concepts of zero code, low code, no code and DSL in examples without reference to specific tools. These approaches appeared in the 1960s, but why is their popularity growing explosively now? What is the special role of the analyst in the implementation of these concepts? What else is there to look at in depth? 
    In this talk, we will try to provide answers to these and other questions. 
    Come – it will be interesting!

    • Average
    • 40 min
    • Analyst Days / 14
  • 01.03.2022
    SOLID and other principles of object-oriented programming in the context of Automation

    Let's all figure out what is object-oriented design, speak about SOLID and other challenging abbreviations and acronyms from the Automation scope. The answers to those common questions - the base of each professional stack of every developer; concepts, which are applied daily; features and complexities at most of the interviews. 

    Come join us - it's going to be interesting.

    • Average
    • 40 min
    • SQA Days / 30
  • 01.03.2022
    Engineering concepts as the basics of Architectural solutions of Automated testing

    We all are used to the variability of the IT world. We have learned to be systematically self-educated. New libraries appear, frameworks, code generators, programming languages. Yearly, hundreds of new books and articles are being published. And we all want a "land of stability", a set of unchangeable principles software works following. 

    Within the scope of the talk, I will try to formulate the most fundamental engineering concepts, which are the basics of every agile Architecture, not depending on the programming language, libraries and frameworks. I will try to show the examples from Test Automation.

    • Average
    • 40 min
    • SQA Days / 30
  • 24.10.2021
    Traceability matrix as infrastructure of communication among QA and AQA specialists

    One of the never-ending topics in IT is "How to organize effective cooperation of specialists at manual and automated QA" with not so much effort required. Let's look at the following solution together: the solution based on granular Traceability Matrix, Test Pyramid and simplest ROI Calculator, and how to integrate those artefacts into TMS with an example of Zephyr.

    • Average
    • 40 min
    • SQA Days / 29
  • 24.10.2021
    AQA Checklist / Score for integrating of Automated testing into existing Agile processes of QA

    Let's all together develop the Checklist and some sort of maturity scale for integrating Automated testing inside existing Agile processes of Quality Assurance. Even a skilled specialist might have issue with adding a new role and activity to the existing process on the project. It's easy to forget essential steps, not to introduce an artefact, not to implement the base level of required metrics, not to define the success and failure criteria, not to forget about priorities and communication with manual testers and developers, to lose visibility of progress and skip on many essential things. A checklist will help you avoid most of the beforementioned mistakes. 

    Join us - it should be interesting!

    • Average
    • 40 min
    • SQA Days / 29
  • 05.06.2019
    Minimum Valuable Product in test automation

    Defining the boundaries and implementation of MVP in software development and wider, in any real sector projects seem one of the most self-explanatory steps, and nevertheless, we're regularly neglect base step while starting the automation. Moreover, we can’t even give a definite explanation, what is automation MVP. 

    In the talk, I am giving definitions and a minimum full pack of information about MVP automation. The material will be useful for QA Managers, QA Leads, and IT Sales Tech Support and automation specialists as an option for a list of prioritized tasks for the first couple of months on the project.

    • Average
    • 40 min
    • SQA Days / 26
  • 16.03.2019
    QA Manager shortlist

    Let's take a look at the main concepts and "tech" questions of QA management: how to form a team, motivate and develop employees, delegate tasks and effectively control their execution, develop responsibility, organise communications. 

    The result of our discussion will be some kind of a checklist, divided into 2 categories: 

    • a list of questions, which requires answers from skilful QA managers; 
    • a list of books \ articles \ recommendations, which should be considered as required to learn before working on such kind of tasks.

    • Average
    • 40 min
    • SQA Days / 25
  • 15.10.2018
    API test Automation – a deep dive into protocol stack

    Our topic covers the most common free tools / frameworks that can be used and integrated into existing framework to automate web services tests.


    1. TCP/IP + OSI Model
    2.  SOA / Micro Services
    3. Client-Service Interaction
    4. REST / Web Socket / Micro Services Testing
    5. Libraries and code samples
    6. Tools analyses

    • Average
    • 1h 30 min
    • SQA Days EU / 1
  • 15.09.2018
    BDD: triangle of Risk Management, QA Management and Tech side

    Behaviour Driven Development in automation testing still generates hot discussions, a backstage dialogue about that approach continued for more than an hour after the SQA Days-21 conference, and the applicability and non-applicability limits, questions about feasibility and effectiveness are still remaining open. We’ve tried to clear up the key points, by devoting 2 talks to the BDD at COMAQA Autumn 2017 Piter conference, but judging by the stormy debate, unambiguous interpretations and exhaustive reasons were not proposed. Let’s try to fix that an unfortunate misunderstanding by looking at the BDD as a triangle of Risk Management, QA Management, and, of course, Tech Side.

    • Average
    • 40 min
    • SQA Days / 24
  • 02.02.2018
    How to pass interview - typical architectural questions


    • Average
    • 40 min
    • SQA Days / 23
  • 04.09.2017
    9 Dante's circles: UI automation anti-patterns

    Let's discuss the architecture of automation from the opposite and focus all our professional attention on the thing "how we should not do", on mistakes and failures contrary to the company's "positive way of thinking". In addition, we will supplement our ideas with systematization, metaphors and "illustrations" from Dante's interpretation of 9 circles. Join us, it's going to be interesting: anti-pattern system with a ton of examples (check-list of architectural cons) covered in literature and mysticism

    • Average
    • 40 min
    • SQA Days / 22
  • 01.05.2017
    Test automation 2018 in examples

    We will talk about the evolution of Selenium WebDriver, and objective reasons, that transformed one of the Web-oriented solutions into web-standard, we will discuss the evolution of tools of mobile automation, we will speak about latest Appium news, we will have a brainstorm about next phase of desktop automation, we will remember kotlin and mention the ar and vr in the context of testing, we will speak about the richness of IoT and AI platforms, complexities of quality assurance today and tomorrow, look at Robotic Process Automation with clear eye, give examples of real projects implemented here and now, and we will join all those elements and formulate the coordinates system and evolutional IT vector using The Sedov's law of hierarchical compensation and Hegel dialectics. Understanding the future of the sector if the industry is the unique advantage. Come and join us, it's going to be interesting

    • Average
    • 40 min
    • SQA Days / 21
  • 24.08.2016
    Pyramid of Testing through ROI

    How to connect two indivisible values Test Pyramid by Mike Cohn and ROI Calculator? How to achieve the synergy for use of both tools?  How to effectively use tools from pre-sales to the post-release? How to adapt solutions for needs of exact project? We'll try to answer those and many other related questions at our conversation.

    Discussion Goals:

    After the training attendees will be able to:

    • Consciously use Test Pyramid by Mike Cohn

    • Combine Test Pyramid and ROI Calculator

    • Adapt instruments for the project

    Discussion Agenda:

    • Test Pyramid by Mike Cohn

    • ROI Calculator

    • Efficient usage from Pre-Sales to the Post-Release

    • Adaptation

    • Examples

    • Average
    • 40 min
    • SQA Days / 20
  • 28.03.2016
    Quality Assurance, Quality Control and QA Automation metrics on fingertips

    Spherical horse in vacuum :)

    Let's formulate and talk about two magical logical chains:

    1. Data

    2. Information

    3. Information relevancy

    4. Information visualization

    5. Decision making - feedback mechanism

    1. Any possible artifacts of Quality control and co - as data

    2. Quality Assurance - as the way of filtering data, forming context and transforming data to information.

    3. Automation testing metrics - relevant to exact project needs

    4. Visualizing information based in introduced metrics

    5. Decision making - adapting process, QA in the best meaning of that word

    Let's try to answer the questions and form the context of the talk about automation testing metrics:

    1. What is the sense of that magical logical chains?

    2. How are they connect with each other?

    3. Automated testing metrics on fingertips

    4. "Value" of the mistake

    5. How to choose metrics relevant to the project?

    6. How to find relevant triggers for putting on "alarm" based on metrics for your exact project?

    7. Visualization

    • Average
    • 40 min
    • SQA Days / 19
  • 05.10.2015
    How to make different motivational models in one cross functional to become friends

    Let's imagine a situation/problem - my personal, overthought about, overfelt, solved... IT company divided into freestanding departments, some of the departments are divided into conditionally independent sub-departments. Non-trivial topology ...

    In every department there is a motivational model used visibly on non-visibly... there is no common motivational model in the company... cross-functional project development, Agile, Scrum, Kanban, their combinations... For clarity (and to be more dramatic) let's take the project as example: PM, Web Front End Development Department Manager, Java Backed Development DM, Manual QA DM, QA Automation DM, DevOps DM. How to organize effective team work? How to solve potential interests conflicts instead of trying to use common motivational model ...? Answers to that and other questions we will try answer from practical and academic-theoretical point of view in the course of our report-dialogue.

    • Average
    • 40 min
    • SPM Conf / 5
  • 30.09.2015
    QA in Agile and Waterfall, is there a difference?

    Let's try altogether to create not even exhaustive and full, but acceptable for all of us classification \ topology of testing types, starting with "wide brush moves" "static" and "dynamic" and finishing with complicated terminological names of exact types. I'll be honest with you - I couldn't find really good classification from the box... even if we speak about world famous certification like ISTQB... That why our work made beforehand is valuable itself... it's important for all from junior specialists to Pre-Sales Technical QA Consultants... this topology is a base for professional coordinate axes of any testing specialist... But we are going deeper: through the cooperatively formulated QA topology we're going to look at software development methodologies not in abstract terms, but in real life, will learn common and different things in Agile and Waterfall methodologies in the QA context. I hope the report is going to be useful not only for QA specialists and PM's but ...

    • Hard
    • 40 min
    • SQA Days / 18
  • 31.01.2015
    Teaching concepts of OOP as an easy way of increasing productivity of a business analyst and a system analyst

    OOP – is a tool to solve domain difficulty problem. Encapsulation – is hiding, but first of all it’s a method of hiding variability and difficulty only after that. Natural contradiction between hiding variability by increasing difficult and hiding difficulty in common sense.  Inheritance and polymorphism as a variant of encapsulation.” Complex systems characteristics as a pack of metaphors for facilitation BA specialist’s everyday job” Have you ever heard such interpretation of OOP paradigm? This approach helps you to understand OOP on a conceptual way only on 3 hours of lectures + some practical classes, specific for you company. What are classes, object… but maybe we need to go deeper – refactoring; idiomatic design and architectural patterns; best planning practices. We will try to solve even wider situation by answering the question “How can you organize such training in your own company by you own powers?”

    • Average
    • 40 min
    • Analyst Days / 4
To leave a feedback you need to

Chat with us, we are online!