Dzmitry Davidovich
Портфолио
EPAM
Project: insurance service. Team: ~400 (whole project)/ ~20 (my block) My responsibilities as a test automation specialist included the following: - writing and keeping up-to-date auto-tests (functional and regression API tests); - code review; - the results of auto-test runs analysis, investigation of test errors; - support and expansion of the existing framework; - knowledge sharing among team members; - interaction with the development and testing group; - work with documents; - participation in stand-up meetings (regularly). During the period of work, I received basic skills, in relation to a real test automation project, in using
Resliv
Project: air tickets retail service. Team: ~150 (whole project)/ ~20 (my block) My responsibilities as a test automation specialist included the following: - writing and keeping up-to-date integration auto-tests (GUI) and CI tasks for their run; - the results of auto-test runs analysis, investigation of test errors; - support and expansion of the existing framework; - interaction with the development and testing group; - work with documents; - participation in stand-up meetings with customer representatives (regularly). Every day I work with linux, at a basic level, I was faced with creating simple bash scripts, and editing previously written ones. - Technology stack on the project: Selenium WebDriver, Selenoid, TestNG, Java, Gitlab, Jenkins. - Worked on kanban, found a little time working on scrum. - In addition to the above, I started maintaining documentation about test automation on a project (began maintaining a section about test automation on the project in the corporate wiki). - I was engaged in the development (addition) of the corporate wiki in terms of test automation.
Elinext
- writing and keeping up-to-date auto-tests (functional and regression UI tests); - code review; - the results of auto-test runs analysis, investigation of test errors; - support and expansion of the existing framework; - knowledge sharing among team members; - interaction with the development and testing group; - work with documents; - participation in stand-up meetings (regularly).