COMAQA Autumn 2017 Piter Сonference is fully dedicated to manual and automated QA in St. Peterburg.
The conference is being organized by the COMAQA.BY community that unites manual and automation QA engineers, developers, devops, managers and other IT specialists in context of manual and automated QA.
We would like to ask you to spend a minute of your precious time and fill the registration form, that information can help us understand how to make the conference even more interesting, what reports are on demand, what main groups of listeners lecturers should be oriented at. The event is free, and that means that we need some kind of free of charge filtering method to find out which listeners are really passionate about the reports, and which of them want to come just for fun – the quality and completeness of filling the registration form is taken as comparison criteria. If the listener is not ready to invest 1-2 minutes for participating in the conference which means the conference is not interesting to him/her, and we should invite more involved participants. In 2 days after registration you will receive an email with confirmation from event organizers.
There are 20 reports in 4 sections:
Test automation (9 reports)
Performance testing (1 report)
Management in testing (6 reports)
Human capital in testing (4 reports)
COMAQA Autumn 2017 Piter Live:
Activist of QA Automation COMAQA.BY, low level Development C/C++ CoreHard.BY, IT specialists, moved to Belarus from other countries InterIT.BY communities and meta-community ITUp.BY, co-founder of DPI.Solutions, manager at EPAM Systems. More than 15 years of experience in IT. Specializes in low-level development, QA automation, management, trainings, and sales.
Senior Development Manager (Solarwinds), backup solution MAXBackup. Activist of QA Automation COMAQA.BY, low level Development C/C++ CoreHard.BY, IT specialists, moved to Belarus from other countries InterIT.BY communities and meta-community ITUp.BY, More than 15 years of experience in IT. Specializes in low-level development and managemt. Used to work at Microsoft \ Hyper-V
Team Lead, Resource Manager. More that 10 years in IT, 7 of them - automated testing. Main zone of interest - Mobile, Backend, API Automation. COMAQA Morning Coffee with automation engineers meetups founder, Automation teacher.
Test Automation Engineer from EPAM. Projects: Parallels, Datalex. Participant of RD Lab, teacher. Breathing fire with style.
Intrigue :) Come and joint us to "know" who the leturer are :)
Chief QA Automation and JDI evangelist at EPAM. Participated in different conferences: SQA Days, Agile Days, IT Week, IT Subbotnik and Eurostar. The author of a couple of open-source frameworks for automated testing: VIQA and JDI. Roman tries to make the world better, help colleagues learn how to test fast, not expensive and with good quality.
More than 10 years in spheres of testing, automation and management.
More than 10 years in spheres of testing, automation and management.
8 years of testing experience. Lead lections on testing. Right now I'm working on testing from T Systems side, and it's a great experience even when you've always been on the other side of the Force =)
9 years in automation. Main area of interest - UI and Web-Services testing, if to be more precise - learning and developing different frameworks and tools.
Human development and testing specialist at EPAM. One of DJs of RadioQA. Came to testing in 2007. Previously worked at different roles: programmer, system administrator and project manager. Read lectures at conferences.
5 years of DevOps in a big search engine development (AlfaLab)
More that 3 years in Automated testing on Node.js. Took part in developing software for learning at EPAM lab and mentoring program. Created and implented some TA frameworks.
6+ years of Test Automation, using C#, .Net, C++, JS in a financial and e-commerce domains. Now I'm focused on testing Web applications using Selenium and JS test frameworks.
About 10 years of experience in IT. Main zone of interest are: Automation using .NET, CI: TFS (vNext,XAML), PowerShell, API Testing, etc.
Speaker is being clarified
The result of our talk about creating effective test strategies is going to be a short cheatsheet-checklist, which answers different questions like: how to develop effective test strategy and measure effectuve \ actuality of the existing one, how to measure and observe the state of the project using metrics, how to propose possible improvements and present them to the stakeholders. Our dialogue is going to consits of "practical part", based on real project examples, and short theoretical base.
It's a regular situation when there is need to create tests for checking system's performance. Moslty, the engineers who implement that task should design and create the workflow of the application and rules of working with it from scratches. In my report I'm going to shown the example of using Gatling load test tool
The report is about the way of creating automation of web-services, and if deeper – how to use Page Object pattern. The main advantage of such approach is it’s maximal simplicity and amity. We’re going to look at the real, successfully functioning framework, build the following way, look at the layers, discuss pros and cons and the idea of the approach itself.
I would like to tell a story about aspect-oriented programming, on the example of Aspectj - an extension for Java and show live examples of how using of that tool can be helpful in building the automation framework.
Many of you heard that when creating test systems we need to understand which layers those systems should consist of. But newcomers or junior specialists sometimes have issues with understanding what are those layers for and which functions they perform. In my report i'm going to clarify those points and answer all the questions.
Behavior Driven Development in Automation still generates discussions, corridor talk about that approach continued for more than an hour after SQA Days 21, and the applicability and non-applicability limits, questions about feasibility and effectiveness are still remain opened. In the dialogue we will try to set the record straight, and formulate the algorithm of applicability and non-applicability of the solution – as the result of the report, in order to make that report as a cheat-sheet for each listener for making BDD solution.
Intrigue! Come and join us, it promising to be interesting...Participate as a listener and active participant of the burning talk :)
Intrigue! Come and join us, it promising to be interesting...Participate as a listener and active participant of the burning talk
The essential part in learning a new discipline is understanding the basics and main definitions. Let us talk about main patterns used in Automated testing: the use of each pattern, patterns of limitation, specifics of implementation, patterns of dependences.
The most difficult part in learning a new discipline - is understanding basics and main definitions. Let's talk about the most popular pattern used in UI Automation – Page Object: using Static Page Object and Dynamic Page Object, bounds of applicability and inapplicability, features of implementation related to content, practical examples.
In my presentation, I'd like to share my personal experience in OpenSource. From contribution in popular projects and publishing my own project on GitHub till participation in the support and development of big company OpenSource solutions This presentation helps you to look on open Source from different sides and understand why this is useful for regular engineer and for the big company
We focus too much on topics related to automated testing. But let's take a look at our everyday work process. How many routine tasks do we accomplish every day? How effectively do we accomplish them? Ivan is going to share his experience on effectively working with such everyday tasks.
Based on experience working as an automation engineer, expert in Java automation assessment committee in Epam, Ivan is going to share general recommendations, advice, materials for those who want to become a Senior automation engineer. This presentation might be useful for Junior and Middle automation engineers who can use it as a guide: find areas with lack of knowledge, what needs to be refreshed, areas to give attention to.
Parallel run of Automated tests is not just a wish, but a real necessity, standard task which sooner or later any project meets. Sometimes, parallel run becomes very difficult or even impossible task. How to avoid such kind of a situation? What recommendations may be used for parallel test execution, what tools are better to use and what architecture for automated tests should be chosen at the beginning? We'll try to answer all these questions and of course will take a look at a dozen of examples to consolidate the proposed material. Then we are going to get focused on the opposite side of the medal and talk about 10 ways of "bad" – hard, slow, expensive, inefficient parallel run of tests on real examples. Our discussion will in fact consist of 2 parts: "what is good and what is bad" - with real examples and recommendations.
Tester and his view on the testing business. How to touch all the hot buttons or reconcile you wish to check everything as in functional testing and check from the business point of view. Establishing such kind of testing, interaction with the development team and testing team. Pros and cons of the participance of skillful testers, instead of people who use the system.
Testing as service - not the most common thing. Even the company with big briefcase prefer internal departments of testing on each project. In the report we are going to talk about turning the department into the "professional service firm" which has come from business management. We will look at pros and cons of that solution, think about unseen issues of migrating to service model of testing.