Friends! We will meet again, January 30, at SPACE event-place, to take part in full-size Saturday's event. We've prepared extended versions of reports from COMAQA.BY activists which were presented at Moscow Conference SQA Days 18 for you. And besides that, three ultimately new reports!
The reporter works in QA from 2006. Main fields of interest are - automated testing using .Net, WindowsPowershell and othe for products for performing automated testing.
COMAQA.BY automation community activist, COREHard.BY hardcore development community activist, co-founder of DPI.Solutions company. More than 13 years of experience in IT. Main specializations: automated testing, C++ low-level development and lower. Management, sales.
Was a system administrator from 2008 till 2014. From September 2014 till nowadays work as QA Automation Engineer at ISSoft (Minsk). COMAQA.BY activist.
In testing from the beggining of 2010. Started as QA Engineer, now work as QA Team Lead. Process-oriented manager, perfectionist, Agile-NOTevangelist, like to automate everything which is repeated more that 3 times and takes more than 1 minute. QA Engineer with good technical background.
QA Automation Tech Lead, COMAQA.BY Activist, IT Academy, IBA Institute and BSU lector, ASP.Net developer. Mostly specializes on functional and performance automated testing of Web and Mobile Applications.
QA Automation Tech Lead, COMAQA.BY Activist, IT Academy, IBA Institute and BSU lector, ASP.Net developer. Mostly specializes on functional and performance automated testing of Web Applications, functional testing of desktop apps.
The author is going to represent the approach of using appllication related XML files as a part of test carcass form Mobile API automation. MS CRM and Mobile API integration is going to be presented as example.
Real automated tests can call themselves automated tests only when a person is excluded from the process of testing. Ideally human part should be only in exploring automation reports which are regularly appear on his mailbox. You can achieve that only in one way - using continous integration tools. What tool is better to be chosen? Why? Is that choice that important or we can use any of them? We'll compare popular java-compatible CI tools and make conclussions!
Automation as a service includes two main tasks: developing automated tests and creating infrastructure for running tests. Second task is going to be described in that report. Docker is lightweight and fast cousin of virtual vms. Just imagine that setting up the environment for running test is easy to pack in some sort of a container with saving all the dependencies, and later - continue development, testing and continous integration in absolutely different environment. Docker helps in solving typical problems, that can appear in deployment and suppoting Continous Integrations. Using Docker helps to avoid system and language conflicts by being isolated in containers, let's you run more tasks with different environment configurations. As the example developing configuration for Docker-container which does CI function for continous run of tests written on Selenium WebDriver is going to be presented during the report.
ow often do you run into the situtation while building processes on the project that exists for dozens of years, but consumer just started working with you and wants to start everything from the blank sheet? In my report i'm going to tell you about: from where to start creating new process on the existing project; how not to repeat mistakes from other teams: i will describe which difficulties you can run into while building processes; how to use the tools that consumer offers and get maximum from them; how to integrate free solutions and prove they are effective and usefull; hot to automate test reports.
Third version of Selenide was released recently. Selenide is a popular framework on Selenium Webdriver for automated testing of web applications on Java. Due to that release i would like to speak about new features of that tool, such as automatic logging, verification, browser control and others.
What does testing in Agile really mean? What is set behind that proud name of Agile Tester? Can we get the answers on those questions, in example, from ISTQB? Are we satisfied with answers? Does that question is actual for Belarusian labor market? Do the departments of Agile testing exist, are the agile testers on demand in Belarus? We're going to speak about all those questions above and make conclusions, which can help us make correct choise and developr our carreer effectively.