Miscsenko Dávid Volodimir

Overview: As part of the Test Automation Framework (TAF) team, I work in a Kanban environment providing shared services across the organization. Our product is an application server that spans multiple generations, from GSM to 5G core, and is used by several larger and smaller R&D teams.

In this role, we are the first point of contact for any issues with the framework, with responsibilities ranging from diagnosing the root cause of problems, fixing them, or notifying the relevant teams for resolution. The main focus of the framework is Functional Testing (FT), and the role aligns closely with DevOps, requiring expertise in Quality Assurance.

Framework's Responsibilities:

• Render configuration and input files during the pre-deployment phase based on the environment and required tests.
• Deploy and execute tests using prepared value files; simulate missing components from the telco core network when needed.
• Capture and analyze test results, ensuring comprehensive evaluation of test runs.
• Integrate with CI/CD layers and pipelines.
• Clean up and ensure the infrastructure is ready for the next test cycle.

Technology Stack:

• Programming Languages: Python (highly OOP, with a large legacy code base), Bash, Groovy, and Go.
• Data Formats: Jinja2 (templates and custom render logic) YAML, JSON, XML, + Jang, and other data interchange formats.
• Microservice Architecture: Docker, Podman (containerization), Kubernetes (orchestration), Helm (releases), Bash, Jenkins (deployment logic).
• Infrastructure: Custom infrastructure on VMware or OpenStack with virtual networks, or public cloud deployment.
• CI/CD & Build: GitLab, Docker-in-Docker (DinD builds), Jenkins, and additional custom tools.

• In 2023 Aprile Won a Shar Tank competition within the company with an idea focused on reducing the carbon footprint using ARM-based CPUs.
• Successfully allocated 60% of my time to the development of a Proof of Concept (PoC) and produced a comprehensive White Paper outlining the concept.
• Gained attention from senior management, including individuals close to the CEO level, for the project's potential.
• Despite initial interest, no decision was made regarding resource allocation or formal commitment, which limited the ability to proceed effectively with the project. The reasons understandable and logical.
• Got the opportunity to continue the project with available resources, but due to a lack of full organizational support, the initiative remained in the early stages.

Overview: As my core responsibilities became routine, I utilized the freed-up time to start building an automated test environment, dedicating around 50% of my time to this effort.
The entire initiative was built autodidactically, driven by self-learning and experimentation.
I successfully developed an automated smoke test suite running on physical devices, rather than emulators or simulators. On bot iOS and Android phone. While the solution had a high maintenance cost, it laid the groundwork for future automation strategies.

Tools & Skills: Python (non-OOP), Appium, Selenium, Selenium Grid, Robot Framework, Xray–Jira integration, basic Git & GitHub.

My first full-time role as a QA engineer, where I was able to structure and deepen my previous testing experience. I had the opportunity to be involved in the birth of a complete product, gaining insights into mechanical, electrical, and software development aspects. At the end of this process, I performed manual testing using barcode scanners and their associated desktop and mobile applications.

Responsibilities:

• This role helped me grow beyond monkey testing and truly understand what Quality Assurance means.
• Executing existing test sets.
• Participating in the development of new features, identifying inconsistencies in documentation, and considering interworking with other features.
• Writing and executing functional, smoke, interworking, and user- based test scenarios.
• Creating and re-testing tickets.
• Conducting exploratory testing.
• Writing white-box tests based on documentation.

I was also responsible for ensuring the quality of our decoder library and mobile SDKs in a complex mobile environment.

Skills & Tools: JIRA, Scrum & Agile methodology, Android & iOS mobile environments.

Overview: I returned to my previous position as a one-man army, trying to catch as many bugs as possible before the release.

Overview: Performed hands-on tasks in a live data center environment, including server monitoring, physical machine installation, cabling, basic OS installation, hardware upgrades, and regular maintenance such as backups and tape replacements.

Handled access control for client technicians and conducted minor troubleshooting tasks, including firmware updates and system checks.

Tools & Systems: Basic use of Zabbix and internal infrastructure monitoring and administration tools.

Overview: Worked 20 hours weekly during university in a fully remote startup environment. My rolle was to understand the newly delivered features and test them based on experience and checklists or just performed exploratory test sessions in a dev environment. Log the bugs and issues using a ticketing system.
Tested the product on both mobile (cross-platform app) and web (primarily Chrome and Safari). I did not participated in the planing and implementation. My responsibility was to cache as many bugs as possible before the prod deployment.
Tools & Technologies: Trello, Planio, MS SQL, Postman, Slack I got some basic overview how the web development works.

• Engaged in direct customer acquisition and promotion of credit cards at high-traffic locations. Assessed customer eligibility, explained product features.