QA: Conference. The second wave of speakers

    There is a more recent announcement:

    Our conference on testing software systems will begin very soon and, as you know, will be held in five cities of Russia. We remind everyone, then we have:
    • from 24 full reports in Moscow and St. Petersburg
    • up to 16 reports - in Novosibirsk and Yekaterinburg
    • 8 reports - in Omsk
    • the opportunity to see the records of all reports - to all participants
    • only full-fledged, 45-minute reports that reveal all the topics “from” and “to”
    • up to 3,000 rubles included: all reports from all cities - in notes, coffee breaks and a huge amount of knowledge

    Which together makes it possible:
    • Get a lot of valuable knowledge in intensive format
    • Transfer your new knowledge to projects and thereby make life easier for your team and company
    • Chat with colleagues on issues that worried you
    • Hear about both positive experiences and negative ones.

    So, the speakers that we will talk about today:
    • Evgeny Ogorodnikov . RmBIT - deploying test automation from scratch - tips from personal experience
    • Sergey Mahetov . IT Center - test automation in Scala
    • Alexey Lavrenyuk . Yandex - methodology and tools for load testing
    • Sergey Pirogov . Automator Notes - Automate Web Application Functional Testing
    • Dmitry Akmaev . DINO Systems - global CI, what it is and what is missing in classic CI
    • Alexander Chumakin . JUNO - automation of scenarios of interaction between integration systems and load testing
    • Ekaterina Bobrova . Tamtek - subject area presentation in autotests
    • Mikhail Bobkov . Neoflex - test automation on integration projects

    Want to read more? Welcome to cat and our site.

    Sergey Pirogov. Automation of functional testing of Web applications

    My name is Sergey, my main specialization is the automation of functional testing of Web applications. I am mainly engaged in the automation of testing the UI part of web applications and the level of web services. He worked on various projects: risk management systems, trading platforms for large banks and eCommerce solutions for large trading platforms. I mainly develop in Java, but the circle of interests does not end there. In my free time I study Groovy. During his work, he used various approaches in testing automation and building frameworks for writing tests. I have extensive experience with BDD tools, such as JBehave, Cucumber. I have experience implementing test automation on a project from scratch, as well as optimizing and improving projects with ready-made automation. There is experience in mentoring and managing a team of 1 to 6 people. According to the wards, he was recognized as the best mentor. I act as a mentor and lecturer at various events. He acted as a speaker at QAFest 2015.

    In general, the report is devoted to the use of Groovy for testing automation purposes. It is based on personal experience working with Groovy and the successful implementation and transition to writing tests using this language. The goal is to show students the capabilities of the language, with which you can write simple and easily supported tests. I will show examples and specific libraries for working with the database, REST API and UI. The description will include tools and libraries that were written independently, for example, GroovyObject or SoftAssert.

    Evgeny Ogorodnikov. We deploy testing automation from scratch - advice from personal experience

    IT specialist with ~ 8 years of experience in various roles: engineer, programmer, tester, testing manager. Twice created from scratch testing, in particular - automation, now in the process of deploying processes in the third. I develop, test and support highly loaded projects mainly in Agile teams.

    In my report, I will talk about choosing a test automation strategy, defining tasks and approaches to the automation process. Test plan, test cases and selection criteria for suitable tests, assessment of the effectiveness and time of task completion

    Ekaterina Bobrova. Presentation of the subject area in autotests

    Leading testing engineer, mainly working on backend projects and projects with a complex structure. I am engaged in the development of test documentation, writing and supporting autotests, CI, manual testing, and training of interns. She worked on projects with test automation for the frontend, backend and API, mainly in Java. Depending on the needs of the project, these were system, integration or unit tests. Most often I developed tests “from scratch”, there was also support and development of another's test suite.

    While working on a variety of projects with test automation, I was able to make sure that the success of automation is invariably influenced by the convenience of organizing test code. Moreover, one and the same code architecture can be convenient in a variety of situations. In the report I will talk about the approach that I like the most. The main part will be devoted to methods for storing test data depending on the complexity of the business logic being tested.

    Sergey Mahetov. Test automation in the Scala language.

    Leading tester. Leading testing specialist at the Information Technology Center. It specializes in testing integration buses for the organization of interdepartmental, interdepartmental, as well as for interstate electronic interaction, including in terms of safety, fault tolerance and performance.

    The report will discuss issues of using the Scala language in conjunction with the test frameworks Scalatest, Specs2, Gatling to automate functional and load testing applications.

    Dmitry Akmaev DINO Systems - global CI, what it is and what is missing in the classic CI

    . I currently manage and develop the Global Continues Integration project. I’ve been testing for 12 years. Worked in companies: Quest Software (Dell), I-Free, since 2011 I have been working in Dino Systems (DINS). I had to use almost all testing methods, including research, performance testing, and even mutational. Not without the creation of their Frameworks.

    In my report, I will consistently tell you: about the history of global CI (a huge connected system of more than 170 types of components, the presence of Legacy code, simultaneous development in 4 countries, complex integration), testing problems that arise in this connection (full test infrastructure is too cumbersome , the update takes a long time, autotests using different approaches and various programming languages, duplication of checks with different teams) and about ways to solve all these problems.

    Alexey Lavrenyuk. Methodology and tools for load testing

    Started by a system administrator about 10 years ago. Then for about a year I loaded the services of banks and telecom, working in an integrator. In Yandex for 4 years, he has been engaged in stress testing, tool development and performance experiments. Leads open-source projects Yandex.Tank and Pandora .

    I will talk about the load testing methodology and our tools:
    • What tests do I need to test to load a typical service?
    • How to configure Yandex.Tank to conduct these tests?
    • in what form to present test results and how to look at them?
    • What tools do we use to automate stress tests and analyze their results?

    Alexander Chumakin. Automation of scenarios of interaction between integration systems and load testing

    For a long time he was the technical leader of a team of 10 people and the main developer of the framework for test automation, mainly based on technologies such as Webdriver, SpecFlow, AutoIt, Sikuli. One run of all tests on one browser took about 7 full days, after which most of the preparatory scripts were transferred to work through WCF services, which allowed to reduce the run time to three days. Another major project is the work in the Scrum team, where from scratch he designed automation for a Big-data project, including testing the Rest and Web APIs, load scripts, full coverage of back-end functionality, including automatic verification of integration with other applications.

    In my report I will talk about back-end testing (tools, technologies and real applications), end-to-end application integration testing, back-end and UI load testing (tools, run platforms, reports), load test automation, brief review of Big-data technologies.

    Mikhail Bobkov. Test automation on integration projects.

    Perform the role of architect on integration projects. Over the past few years, I’ve been working on one of the largest integration projects of CSS. I am an ideological inspirer and architect of a system for automating testing of integration projects

    Integration solutions are created to connect systems with each other. One of the problems in testing on such projects is that it is not always possible to use real systems. A way is needed to replace these systems with stubs, but integration scenarios are complex and behavior varies with the data. In this training, an introduction to integration will be given for students who are not familiar with this area. As part of the report, the main problems of testing integration solutions will be announced and how we at Neoflex solved these problems. A comparative analysis of technologies will also be provided, which was considered to make a decision on creating a system. And the system itself is represented

    When and where?

    Registration links:

    I have something to tell

    If you have something to tell, welcome to us: we are looking for speakers. Tell everyone about your experience in testing automation, because it is experience that saves everyone valuable man-hours and increases both the level of a specialist and the level of remuneration =)


    Also popular now: