
There is a more recent announcement:
https://habrahabr.ru/company/luxoft/blog/280524Our
conference on testing software systems will begin very soon and, as is known, will be held in five cities of Russia. We remind everyone, then we have:
- from 24 full report 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 - all participants
- only full-fledged, 45-minute reports covering all topics “from” and “to”
- up to 3,000 rubles included: all reports from all cities - in the notes, coffee breaks and a huge amount of knowledge
What together gives the opportunity:
- Get a lot of valuable knowledge in intensive format
- Transfer your new knowledge to projects and thereby make your team and company life easier
- Chat with colleagues on issues that you are worried
- Hear both about positive experience and about negative
So, the speakers, which we describe today:
- Evgeny Ogorodnikov . RmBIT - we deploy test automation from scratch - tips from personal experience
- Sergey Makhetov . IT Center - Test Automation in Scala
- Alexey Lavrenyuk . Yandex - methods and tools for load testing
- Sergey Pirogov . Automator Notes - Automation of functional testing of Web applications
- Dmitry Akmaev . DINO Systems - global CI, what it is and what is missing in the classic CI
- Alexander Chumakin . JUNO - automation of integration systems interaction scenarios and load testing
- Catherine Bobrova . Tamtek - representation of the subject area in auto tests
- Mikhail Bobkov . Neoflex - testing automation on integration projects
Want to read more? Welcome to the cat and to
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 mainly deal with the automation of testing UI parts 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 it in Java, but my circle of interests does not end there. In my free time I study Groovy. During his work he used various approaches in test automation and building frameworks for writing tests. I have extensive experience with BDD tools such as JBehave, Cucumber. I have experience in implementing test automation on a project from scratch, as well as optimizing and improving projects with ready automation. Have experience in mentoring and managing a team of 1 to 6 people. According to the wards, was recognized as the best mentor. I act as a mentor and lecturer at various events. Served as a speaker at QAFest 2015.
In general, the report focuses on the use of Groovy for test automation purposes. It is based on personal experience with Groovy and successful implementation and transition to writing tests using this language. The goal is to show students the possibilities 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. Deploy test automation from scratch - tips from personal experience
IT specialist with ~ 8 years of experience in various roles: engineer, programmer, tester, testing manager. Twice he created testing from scratch, in particular - automation, now in the process of deploying processes in the third. I develop, test and support high-load projects mainly in Agile teams.
In my report, I will talk about the choice of test automation strategy, the definition of tasks and approaches to the automation process. Test plan, test cases and criteria for the selection of suitable tests, assessment of the effectiveness and time of task execution
Catherine Bobrova. Representation of the subject area in autotests
Lead testing engineer, mainly working on backend projects and projects with a complex structure. I am engaged in the development of test documentation, writing and support of autotests, CI, manual testing, training of trainees. 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 someone else's test suite.
During my work on a variety of projects with test automation, I was able to ensure that the success of automation always affects the convenience of organizing test code. Moreover, one and that code architecture can be convenient in various situations. In the report I will talk about the approach that I like the most. The main part will be devoted to methods of storing test data depending on the complexity of the business logic being tested.
Sergey Makhetov. Test automation in Scala
Lead Tester Leading specialist in testing the company Information Technology Center. Specializes in testing integration tires for the organization of intradepartmental, interdepartmental, as well as for interstate electronic interaction, including in terms of safety, resiliency and performance.
The report will discuss the use of the Scala language in conjunction with the Scalatest, Specs2, Gatling test frameworks to automate the functional and load testing of applications.
Dmitry Akmaev DINO Systems - global CI, what it is and what is missing in the classic CI
Currently, I manage and develop the Global Continues Integration project. I have been doing testing for 12 years. He worked in companies: Quest Software (Dell), I-Free, since 2011 I have been working at Dino Systems (DINS). I had to use almost all methods of testing, including research, performance testing, and even mutational. Not without the creation of its Frameworks.
In my report, I will consistently tell you: about the background to the emergence of global CI (a huge connected system of more than 170 component types, the presence of Legacy code, simultaneous development in 4 countries, complex integration), the testing problems that arise (full test infrastructure is too cumbersome , updating takes a long time, auto-tests using different approaches and different programming languages, duplication of checks by different teams) and about ways to solve all the problems listed.
Alexey Lavrenyuk. Methods and tools for load testing
He started as a system administrator 10 years ago. Then, for about a year, he loaded services of banks and telecom, working in the integrator. In Yandex for 4 years, engaged in load testing, developing tools and experiments in the field of performance. Leads open-source projects
Yandex.Tank and
Pandora .
I will talk about the load testing methodology and our tools:
- What tests need to be carried out to test the load typical service?
- How to configure Yandex.Tank to conduct these tests?
- How to present the test results and how to look at them?
- What tools do we use to automate load tests and analyze their results?
Alexander Chumakin. Automation of integration systems interaction and load testing scenarios
For a long time, he was a technical leader of a team of 10 people and the main developer of a 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 scenarios were transferred to work through WCF services, which reduced the run time to three days. Another major project is to highlight the work in the Scrum team, where from scratch I designed automation for the Big-data project, including API Rest and Web testing, load scripts, full back-end functionality, including automatic testing of integrations with other applications.
In my report, I will talk about back-end testing (tools, technologies, and actual use), end-to-end application integration testing, back-end load testing and UI (tools, platforms for running, reports), load testing automation, a brief review of big-data technology.
Mikhail Bobkov. Test automation on integration projects
I fulfill the role of an architect on integration projects. The last few years working on one of the largest integration projects UBS. I am the inspirer and architect of the system to automate the 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 plugs, but integration scenarios are complex and the behavior changes depending on the data. In this training will be given an introduction to the integration for students who are not familiar with this direction. The report will highlight the main problems of testing integration solutions and how we solved these problems at Neoflex. There will also be provided a comparative analysis of technologies that has been considered for making decisions about creating a system. And the system itself is presented
When and where?
Registration links:
I have something to tell
If you have something to tell, you are welcome to contact us: we are looking for speakers. Tell everyone about your experience with test automation, because it is the experience that saves everyone valuable man-hours and increases both the level of a specialist and the level of remuneration =)
Contacts