BIO: I’ve been working on big Manufacturing system that became a part of Siemens company and one of the biggest Mfg company in the world. I was a team lead of 10 members automation team. We had tens of thousands GUI tests with preparation data on server side using WCF services of our ASP.NET system.
Then I worked in Adform company that is one of the biggest Advertising companies in Europe that provide all solutions for targeting advertising. I worked with backend API testing, performance, security, and almost all other possible test layers.
Now I’m working in famous USA startup Juno that R’n’D center is located in Minsk. I am a quality engineer of backend team. I’m working with microservices testing and included in all stages of product development.
During all my experience I was a mentor of many QA members, prepared different internal talks about QA Automation for all level specialists. I had some talks in Minks QA meetups that is performing regularly by different QA communities.
Also, I was a speaker in international conference qaconf.ru in April, 2016 in St. Petersburg and May, 2016 in Moscow. In this February I was a speaker in seleniumcamp.com in Kyiv.
Presentation followed with panel discussion: Honest, simple and fast isolation tests.[ENG]
This is about how we test microservice system in our Juno company using isolation. It should contain some basic idea of how to organize microservices testing, why it should be tested in isolation, how to use wrapping, brockers simulation. I want to show that the idea is quite simple, tests are super stable and fast. And I will explain our processes in project, how we work with developers and other quality engineers in big back end team.
The main idea is describe how to make isolation tests really honest, why should we make it, how to organize project to support it very easy, how to make tests easy to read and understand etc.
Anyway, there will not be a lot of examples, only basic ideas, may be a few easy tests to show how wrapping and interceptor work. This is a talk for strong audience that have experience at least with some back end testing like API Rest. Otherwise it will be useless for all other participants.