Padmi
FreeBalance logo
FreeBalance

Government Resource Planning (GRP) · Public Financial Management (PFM)

Senior QA Automation Engineer

Warsaw · OnsitePosted 2 months ago
Software QualitySeniorFull Time
Apply at FreeBalance

Opens the source posting on jobs.lever.co

Source description

About the role

View original

Automation Framework Architecture & Development ● Design, build, and maintain a scalable Java-based test automation framework using Playwright for UI and REST Assured for API testing. ● Establish framework architecture decisions: project structure, base classes, page object model, test data management, reporting, self-healing and retry logic. ● Define and enforce automation coding standards, naming conventions, and documentation practices. ● Build reusable utility libraries for common actions: authentication flows, environment configuration, database queries, and assertion helpers. ● Ensure framework supports parallel execution, cross-environment configuration, and CI/CD integration from day one.

UI Test Automation (Playwright + Java) ● Implement end-to-end UI test suites covering critical GRP workflows: budget execution, expenditure processing, treasury payments, and revenue collection. ● Apply Page Object Model (POM) pattern to ensure test maintainability as the UI evolves. ● Handle complex JSF-based UI interactions including dynamic forms, multi-step workflows, modals, and data grids. ● Build smoke and regression suites that can be triggered automatically on each build artifact. ● Manage test data setup and teardown strategies to ensure test isolation and repeatability.

API Test Automation (REST Assured + Java) ● Design and implement comprehensive REST API test suites covering GRP service endpoints across all functional modules. ● Validate API contracts: request/response schema, status codes, error handling, authentication, and data integrity. ● Build data-driven API tests that cover boundary conditions, negative scenarios, and multi-step transactional flows. ● Integrate API tests as a fast-feedback layer in the CI pipeline, running on every Trunk commit independently of UI tests. ● Collaborate with back-end developers to define testable API contracts and flag integration issues early.

CI/CD Integration ● Integrate automated test suites into the existing Jenkins CI pipeline, triggering appropriate test layers on each build. ● Configure test execution stages: smoke on commit, regression on Code Freeze, full suite on release candidate. ● Implement test reporting and failure notification so the team receives actionable feedback without manual monitoring. ● Work with the DevOps team to manage test environment provisioning and ensure automation runs reliably across environments. ● Maintain pipeline stability: monitor flaky tests, enforce quarantine processes, and drive flakiness reduction.

Test Coverage Strategy ● Collaborate with the QA Lead and Manual QA Engineers to identify and prioritize automation candidates based on risk, frequency, and regression value. ● Build and maintain an automation coverage map showing which manual test cases have been automated, which are in progress, and which remain manual. ● Define and track key automation metrics: coverage percentage, execution time, pass rate, and flakiness rate by module. ● Contribute to shift-left testing practices by enabling developers to run smoke suites locally before committing.

Cross-Team Collaboration ● Partner with Manual QA Engineers to convert high-value regression test cases into automated equivalents. ● Work with Functional Analysts to understand business workflows deeply enough to write reliable automation for complex multi-module flows. ● Participate in sprint planning and backlog refinement, estimating automation effort and flagging testability concerns during requirements review. ● Support developers in understanding test failures and distinguishing automation issues from genuine application defects

Mentorship & Continuous Improvement ● Mentor Manual QA Engineers interested in developing automation skills. ● Conduct code reviews on automation contributions from other team members. ● Continuously evaluate new tools, libraries, and practices that can improve framework efficiency or coverage quality. ● Document framework onboarding guides to enable team members to contribute automation without deep framework expertise.

One address, no account. We’ll tell you when matching roles go live.

More at FreeBalance

Related open roles

View all roles