COMAQA Spring 2017 Сonference is fully dedicated to manual and automated QA.
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.
There are more than 20 reports , divided into 6 sections:
Automated testing (7 reports)
Management in testing (4 reports)
DevOps (5 reports)
Human funds in testing (3 reports)
Testing and data (1 report)
Special types of testing (1 report)
Activist of QA Automation COMAQA.BY and low level Development C/C++ CoreHard.BY communities, 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.
Test Automation Engineer from EPAM. Projects: Parallels, Datalex. Participant of RD Lab, teacher. Breathing fire with style.
Works at EPAM Systems in Vitebsk. Has experience in testing web and mobile applications, Java and .Net application.
4 years in QA, but managed to work on projects for mobile, web and a bit of gamedev, and teach a group of high-level QA Juniors (6 of 7 managed to find job in the first two weeks), HTML code and develop a couple of sites using CMS. Right now the main activity is Automation using PHP.
Main experience in IT is in system administration, almost two years of experience with automation based on Selenium around Java ecosystem. Previous system administrator experience helps in solving errors of test run infrastructure.
More than 5 years in automation. Worked mainly with UI Automation, also have experience in different platforms: Web/Desktop/Mobile. Favorite tool – Selenium WebDriver and “Selenium-like” solutions. Area of interest right now – designing and implementing architecture and processes of automated testing. COMAQA.BY activist, lector, teaching Automation in training centers, companies, universities.
Resource manager, lead software developer, about 7 years of experience in IT: software development, QA, building business processes, risk management. Evolved from an qa engineer to the developer and group lead, project manager.
More than 5 years of experience, about 5 years in security. Main specialization: pentesting, additionaly worked: ERP, IB, SIEM. Hacked half of bynet, participated in bug bounty, worked with major and popular projects, banks, telecoms. Like to go to the sea, carting/ATVs, swimming. OpenStack, Kali, Python/PHP/Bash/(My|MS\Postgre)SQL, RHEL/Debian, working with security tools, IBM QRadar/RSA EnVision.
More than 14 years in IT. In Automation, main specialization is integration, load and testing using Java tech stack. Mainly work in projects for one of the most difficult enterprises – banking. Have experience in managing projects, business-analysis, development.
More than 10 years in spheres of testing, automation and management
Evolved from monkey clicker to automation engineer in 3 years. Love testing. But can’t exactly say that.
Test Automation Team Lead in SolarWinds, COMAWA.BY activist, lector at multiple training centers. Main specialization in automation is functional Web and mobile testing.
8 years in IT. Primary areas: software development and automated testing. Architect and key developer of ReportPortal at EPAM Systems.
About 9 years of testing experience. Work at PandaDoc. Recent job is Test Lead in Testing Competency Center at Epam Systems, trainer about test strategies.
Business consultant, specialist in the field of processes, service, quality, teaching the staff. 7 years of experience in the team development.
7 years in Test Automation, focusing on UI and Web-Service automation using Java and сomplementary technologies.
A little experience in manual testing, performance testing and security testing; main specialization – automated testing using WebDriver with Java bindings.
Main specialization – system administration, Java development, teaching. Recent years’ activity is focused on DevOps.
Test Automation Team Lead at Epam Systems, more than 5 years in Automation, main specialization is Java stack for Web-Automation and a little of Mobile and Web-Services.
Docker is a very useful tool, to build required infrastructure only at the time of test run (browsers of different vendors and version of isolated containers, help stud-services, etc) in seconds. Browsers in containers lets you parallelize the test run – that enormously shortens the test run time, provides clean environments for each auto-test – which increases test stability. Containers, in contrast to VM are much easier to create and kill, which helps in save our funds. In short about Docker on Windows. Description of Selenoid working principles - https://github.com/aandryashin/selenoid - why it’s better than HUB or HUB on Docker. Possible demo based on the topic verification and Docker basics demonstration running Jenkins and a couple of automatically connected Slave with “one command”, running and demoing Selenoid.
Docker, as technology, is intensively used for a long time in various projects. The report is about the variants of using Docker for automated testing on such projects like: micro services deploy verification, building isolated environment for testing, monitoring production state.
In the report, we are going to speak about feature and tasks, which appear if front of the automation engineers of complex systems. We’re going discuss the solutions which we implemented for integration automation of complex solutions. I will show how DevOps and automation lets you build automated testing systems.
Tests paralleling: the best PHP tool for automation (Codeception); basics of Docker; robo – what is it and why we need it; profit.
The report is an overview of various tools for testing using Python, which can be used for creating effective end-to-end framework based on Selenium WebDriver with minimal number of self-implemented wheels. We are going to look at such architectural components like wrappers around driver itself, Page Object and Page Element patterns, reporting and following tools, which are going to work and play a role of those components.
What to do if you need to implement automation but there is no team of 10 automation engineers and not planning to be. The reporter is going to describe how to create automation from the scratch fast and effective by one person. During the presentation you are going to learn how to start building automation framework for UI and API testing.
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.
There are tons of talks on how to build automation properly, however there is no silver bullet for every problem and here’s where people get in trouble. They can’t apply the “perfect” approaches and practices so they try to implement their own and often make common mistakes. Those “mistakes” aka “what NOT to do” aka “antipatterns” that we’re going to talk about. I’d like to mention both coding antipatterns and antipatterns in the whole approach to automated testing that I’ve come across too often and that often prevent growth of the project. Hopefully together we will be able to avoid those common misconceptions.
Company Management is trying to make solution not like “as it goes”, but based on numbers and data. How to test the work of software which calculates that numbers? If the code, which processed the company’s year data calculated 42% - is it a correct answer, or we have a mistake here and we should receive 43%? I would try to answer that question based on the practice we have collected in the analytic department in Toptal. BI, ETL, DWH, ML… If you know what those abbreviation mean – come and join us in a talk about testing in a world of data.
Testing is a process, which does not remain where it is and requires continuous improvements. We’re going to that during retrospectives, from personal or somebody’s experience and mistakes, intuitive or based on some kind of data. I will describe how to value the testing process on the project: where to start from, where to pay more attention, share my practical experience and answer all your questions. See you at the report.
Soft skills – are person’s skills, which are not connected to his professional skills, such as honesty, goal persuading, leadership. In the most cases those skills make an employee valuable, or not valuable and unbearable regardless his or her professional skills. For “starting” positions, where experience is not a goal, soft skills become especially actual. During the report we are going to create a profile of soft skills for the employee working in testing and look at the methods of finding those skills.
That story is about everybody who met the problem of motivation at least once. The story is for people who is going to meet that motivation problem. Who is guilty, what to do and how to live with that?
In a short report the example of unsuccessful automation is described. Automation which lead to the team demotivation, unstable tests, pointless time waste and to unsatisfied customer. Automation stack: API (Exchange, REST, Azure), DB, Windows PowerShell, TFS, MSTest.