Jack Gittins
Senior Quality Engineer
Dedicated Quality Engineer with over 8 years of experience in software testing and a background in Geographic Information Systems (GIS). Proven expertise in both manual and automated testing across responsive web and mobile applications. Passionate about accessibility testing and mentoring team members in automation practices. Committed to continuous learning and improvement, I aim to drive quality and efficiency in software delivery.
Career Aspirations
Building on my automation expertise, I am currently exploring how to seamlessly integrate
accessibility testing directly into our CI/CD pipeline, potentially leveraging tools like Axe-core
with Playwright. My goal is to make these checks automated and routine, allowing us to catch and
address compliance issues early and efficiently. This technical integration ensures that
accessibility is a scalable and sustained part of our testing strategy.
While automation is key, I deeply understand that a comprehensive approach to inclusive quality requires
manual auditing and user-centric testing. I possess proven skills in manual accessibility testing,
including proficiency with assistive technologies like screen readers and keyboard-only navigation
testing to fully evaluate the user experience for individuals with disabilities. Furthermore, I actively
advocate for these practices by creating documentation on how to test for the WVAG requirements and
have had 1 on 1 sessions with other engineers to help them understand the guidelines.
Code Examples
E2E Automation
Page Object Model (POM) is something that I have more recently learnt and begun using. I had been using similar concepts for my automation data in a variable file for reusability, and found that a POM did the same but for test code. I enjoy writing in this model not only as it is easier to reuse across tests, but also because it is much more maintainable as changes only need to occur in the helper file rather than in all the tests. Additionally, when writing out a test, POM makes it more readable. If it has been set up well, less time can be spent looking on the User Interface (UI) for locators, making it faster to write tests.
API/Cucumber
I have experience in writing automation in playwright (example below), cypress and cucumber. I like playwright as its fast and unopinionated. I enjoy cucumber aswell, I like how it can be used across teams with Business analysts writing the tickets in way that can be used in automation, this is something that I see as useful especially in a client services type of role. Being able to leverage existing tests and build up our library so it can be quickly set up for new projects is super useful when on tight deadlines.
Test Reports
Since moving to Playwright, I have primarily been using the built-in reporter. I find it extremely useful for filtering tests, viewing just passed or failed tests, viewing tests for specific browsers, as well as for its ability to tag tests as flaky. I have identified that built-in screenshots is a valuable missing component, and I have added this in the code. In using Cypress, I would typically set up mochawesome to achieve similar results for the reports.
Accessibility
In accessibility testing, I value both manual and automated routes. I believe that both are important as there are some components that cannot be automated, and others that may not be worth the effort of automating. There are, however, libraries for automation that I find very valuable. Axe-core is a tool which I have experience in integrating with both Cypress and Playwright. I find that it is configurable and consistent, and that Deque as a company are always quick to update their tools to meet the latest accessibility standards.
Automation Values
For test automation, I value readable and maintainable code. I believe that maintenance
often gets forgotten about when working with automation suites. I've found that a POM
helps very much with cutting down maintenance effort; it also keeps the tests easy to read
and understand.
Similarly to readable code, I believe that commit messages are an important skill to use. Being
able to explain the code being pushed has helped me to grow my skills and properly understand
each line. It also makes it easier for others to review and approve or suggest improvements
to merges.
I believe that reporting is very important in an automation suite. If and when tests fail,
it is key that we are able to identify what has failed, how it failed, and narrow down the
root cause of the problem. Debugging a test and finding out in a timely manner if it is an
application issue or the test script is a high value for me in an automation suite.
Projects
Rebuilt the Grill'd digital experience. iOS and android ordering apps and the marketing website/web ordering
A website for tracking scouts progress through their journey with multiple user roles
A WCAG 2.1 AA standard website to help people understand life with Cerebral Palsy
A mobile game to help perserve the Nyiyparli language and culture
A suite of apps to help conserve whales in the Vancouver Bay Area. Seperate apps to report and alert pilots
Programs Experience
Project Management
Test Case Management
Automation Framework
Performance/Load Testing
API Testing
Headless CMS
Accessibility Testing
Database
Mobile App Beta Distribution
CI/CD
Error/Crash Monitoring
Analytics
Career and Education
Dept ® (formerly twobulls)
May 2021 - Ongoing
- Lead testing efforts for responsive web apps and mobile applications, ensuring compliance with varying requirements.
- Conduct accessibility testing to meet WCAG 2.1 AA standards.
- Design, build, and maintain automation suites using Cypress and Playwright.
- Gained experience with Maestro for mobile automation.
- Perform load testing using k6 to evaluate application performance.
- Utilize Postman for REST API testing and Proxyman/Charles Proxy for monitoring and mocking API responses.
- Familiar with AWS automation.
- Assist in the creation of user stories with clear acceptance criteria.
- Manage project tasks using ClickUp and Jira; employ Zephyr-Scale for effective test management.
Lapis (part of Spatial Vision)
December 2017 - May 2021
- Operated within the agile software delivery lifecycle, delivering high-quality products free of critical bugs.
- Developed automated end-to-end regression tests using Cypress, enhancing testing efficiency.
- Gained project management experience by conducting client stand-ups and drafting user stories.
Spatial Vision
September 2015 - March 2018
- Engaged in GIS software operations to update and maintain spatial data
- Produced cartographic products