Oleksandr Polazhynets

An ASP.NET-based set of web applications that connect customers with questions and experts who can answer these questions.

I was the QA lead in a team of three QAs, supervising all QA activities, including verifying requirements with product owners and designers, ensuring that developers understood requirements, testing releases manually or automatically, and supporting customer service agents in production. In addition to the QA lead role, I was a Scrum master responsible for following the Scrum principles and artifacts usage such as regular meetings. From a technical perspective, I adopted TestRail as a test case management tool and created a framework for running E2E tests using Selenium and NUnit.

As a single QA in a team that worked on a blog website, I oversaw all QA activities, including:
• requirements analysis,
• test documentation maintenance,
• manual and automated black-box test cases,
• test execution and test artifacts generation and presentation to the stakeholders, and
• release process support, testing logs, and metrics monitoring.

As a part of automated testing, I set up mobile testing using Appium and Android VMs and connected it with Selenium Grid.

In a company delivering features on demand, I worked as a QA on the process of continuous testing, which included more automation on low levels (unit and integration) and less E2E and manual testing by QAs, the so-called testing pyramid.

In the scope of that process, a new testing paradigm was created, which involved developers in the QA process, so testing became a responsibility of the whole team, not just QAs. From a technical perspective, I investigated tools for functional testing on the front end, such as Playwright. I worked on a visual testing engine that could capture screenshots on different devices, send them to the screenshot comparison tool, and generate a report.

I created a test engine that allows running integration tests for the .NET Core web service and web app in memory. In other words, the client doesn't have to host the application in any environment, avoiding issues with environment setup or network configuration. An engineer can purely test the application logic.

Set of PowerShell scripts and Jenkins pipeline that allows an engineer to create:
• .NET Framework and .NET Core application with common logic, configurations, and logging.
• PowerShell scripts to build an app within a Docker file and scripts for deployment.
• Docker file to run that app.
• Helm chart to deploy that Docker image into Kubernetes cluster, which contains configuration map and Ingress controller.
• Jenkins pipelines for building and deploying artifacts.
• Kibana monitoring and Grafana dashboard with basic metrics CPU, memory, and disk I/O.
• Git hook that would trigger build pipeline when changes were pushed to source control.
• Email and Microsoft Team notifications for building and deploying pipelines.