Position: Test Automation Engineer
Company: Movianto
Category: QA Automation
Experience required: 2y
English level: fluent

Key responsibilities:

Be part of a small QA Team for a complex system with a big push on automating a largely manual test library. 
The role would suit somebody with existing experience in test automation looking for the opportunity to steer and shape a fledgling Test Framework. 

However, a manual test engineer with strong aspirations to move into test
automation, with relevant business, project, or technical background would also be of interest.

While the tool of choice for the project is Katalon, direct experience with Katalon is not a prerequisite.

**Be the QA representative assigned to a scrum with responsibilities for:**
• Defining the test strategy for new user stories.
• Contributing to the development of acceptance criteria.
• Identifying positive and negative test scenarios.
• Working with developers to accept delivered Integration Tests.
• Implement new automated business logic test cases.
• Executing tests (manual and automatic) and triaging defects back to Development.
• Demonstrating results to the customer.

**Help to drive the direction of the test automation framework, including:**
• Proposing designs for new or improved classes and methods to implement
automation building blocks.
• Working other QA Team members and Development to shape the technical
direction.
• Implementing test cases in Groovy and BDD.
• Seeking opportunities where the framework could be optimised, extended or
rationalised.
• Developing processes to make the work of the QA Team more formalised,
predictable and reportable.
• Working with other teams within Honeywell and the customer to ensure
interoperability of tests and processes.
Previous business or related project experience

Any of the following would be directly useful:
• Tobacco or any FMCG (i.e. Pharma)
• Logstics/supply chain/SAP/CRM
• Track and Trace, GS1, TPD, FCTC
• Scanning solutions/barcode standards
• Mobile device app development
• High volume throughput cloud-based systems
• Mission critical or compliance related systems

**Project environment**

• Experienced with Agile and working in scrums
• Comfortable working in teams upwards of 40-50+
• Remote working, particularly across multiple countries
• Direct engagement/involvement with the customer
• Comfortable in working with evolving requirements
• Fast-moving, sprint-driven, frequent parallel releases

**Previous testing experience**

Experience in a number of the following categories would be essential:
• Test planning, design and scripting
• Functional testing
• System Integration Testing
• Negative testing
• Performance testing
• User acceptance Testing involvement
• Regression
• Test Automation
• Behaviour Driven Development (BDD)
• REST/API Testing
• Web/portal/mobile testing

**Technical knowledge**

Specific tool knowledge is less important than what you have done with them:
• Katalon, Postman
• Ranorex, Appium, Selenium
• Java, Groovy, Cucumber
• Jira, X-ray
• JMeter
• Web services
• XML
• EPCIS

**Personal profile**
Any of the following characteristics would be useful:
• Be a self-starter. You should not be put off by a lack of structure or process and be prepared to step in and fill gaps where they exist.
• Have a willingness to share test artefacts, knowledge or process improvements with the rest of the team.
• Think holistically: be prepared to challenge specifications and solutions and question everything.
• Focus on reuse: keep an eye as much on what will be needed to do this next time.
• Ability to timebox: we work to strict deadlines and need to manage time effectively.
• Have a sense of humour.

Any previous experience in helping to design and shape a test automation framework would be especially useful, including:
• Setting the business architecture for the framework, including a vision of where it needs to go.
• Finding the right balance in technical implementation between ease of maintenance and ease of use.
• Script parameterisation and use of variables to extend test coverage.
• Standards and best practices, i.e. structure, naming conventions, maintenance practices.
• How to integrate tests with external data sources and tools.
• Defining conditional logic in test cases, making tests self-cleaning and self-correcting.
• Integration of automated tests with CI/CD pipelines
• Implementing metrics, KPIs, and reporting, to monitor framework performance.