Regular QA Automation

at  Luxoft

PROJECT DESCRIPTION

About Surveillance & Regulatory Surveillance and Regulatory Technology is part of Corporate Bank Technology and responsible for delivering solutions that protect the bank’s financial and reputational interests from potentially criminal or inappropriate behavior by our clients, employees, vendors. It enables the bank to manage its compliance to regulations and the risk appetite to stay in business in the various legislation. In addition, the function, is responsible for driving improvement across the IT delivery cycle through adoption of best practices, automation tooling and metrics, as well as developing a target state DevOps capability. Application is the front gate into the Surveillance Domain and the glue between all the Surveillance Controls that analyze the transactions. This is the place where it is decided which Surveillance Controls need to be run and where the analyses are being consolidated into one final decision. Big amounts of data (millions of messages per day) need to move fast (some as fast as 200ms) and reliable. Data loss is not an option and self-healing is mandatory.

SKILLS

Must have
min 3 years experience as Automation QA Engineer (Java);
Experience with JIRA Structure;
JMeter experience;
Cucumber
Nice to have
OpenShift

We are looking for a QA Automation Engineer that can help us automate application to as close as possible to 100%. Our philosophy is, we only do a manual test scenario once, the second time it runs as an automated test. We are not there yet, so do expect manual testing will be required as well. Our testing necessities come not only from asserting the quality of the application but also from being able to demonstrate to different stakeholders that certain scenarios have indeed been tested. Considering the stakeholders have different levels of technical understanding, our weapon of choice is Java with Cucumber. Application job is predominantly to move data and ensure resilience and fault tolerance, so there is a big focus on non-functional testing, but functional testing is also important in areas such as eligibility and data-mapping or analyses consolidation. It is worth noting that we also have version of application in prod that we are trying to bring to the point where no further development is required. But even in this scenario, regression testing every few months at least will be required. The test packs for these are ran with JMeter. Technologies:
Java
Cucumber
JMeter
OpenShift (nice to have) Platforms:
Jira
ALM Responsibilities
Test Planning: Collaborate with the QA team and development stakeholders to understand project requirements, define test objectives, and create a test strategy and plan for automated testing.
Test Automation: Develop, maintain, and execute automated test scripts using automation testing frameworks and tools. This involves writing code to simulate user interactions, data inputs, and expected outcomes.
Manual Test Execution
Defect Reporting: Identify, log, and track defects found during testing in a systematic manner, working closely with the development team to ensure timely resolution.
Test Documentation: Create and maintain documentation related to test cases, test scenarios, and test execution results.
Collaboration: Work closely with cross-functional teams, including developers, business analysts, and product owners, to ensure smooth communication and understanding of requirements.