Ryan Dalton

Accomplished Automation Tester with 4+ years of experience using analytical and technical expertise for optimum delivery to business. Adept in the design, creation and execution of API, UI, and Functional tests. Specialist knowledge of testing, API, and data management tools.

Current Role - Tombola PLC Test Automation Engineer (6 years in industry)

As part of my current role I am required to use a range of different technologies and skills in order to achieve the targets presented to me by the business. Examples of these are listed bellow:

• Programming Languages : My day to day requires me to use Playwright using type script to create test step definitions to automate our testing. The framework is written in Java and where required I use my skills in Java to write code in order to reduce the number of steps required to complete a scenario within the story we are testing.
• Programming Tools : I develop my test scenarios using either Visual Studio, with previous experience in Eclipse and Intellij. I will typically use GitHub to pull down a projects repository and create my own personal branch, and begin working on test executions, functions, and framework code for automation purposes before pushing and merging the branch into the original project.
• API Testing : As part of my testing background, much of my time has been spent on dealing with Mobile and Web applications that have both a Client and Hybrid view, both interact with the Gateway and require API testing through tools such as Postman, Insomnia, or SoapUI. This testing routinely looks at success scenarios, error scenarios, and RAML scenarios.
• Project Tracking : The fundamental part of my role is locating bugs and defects that may arise from further development of the project. I am intimately familiar with using Jira for the last 6 years for reporting, planning, and tracking these bugs and defects. Furthermore I have used Jira as a means for monitoring and tracking our test work load using GenJira tools such as Kanban Boards in order to keep organized for feature and backlog testing.
• Non-functional Testing : Depending on the requirement of the story I will be required to action Non-functional testing such as security checks, stress tests, and Gateway upgrading testing.
• Automation Testing : Currently all automation I personally run is either local on my machine, through TeamCity runs, or through a Jenkins builds - all will use tools to run automation such as SeeTest/Browserstack for cloud mobile devices, or PlayWright for browser applications.