QA Lead @ Projector Inc.
As the first hire in QA at Projector, Jeff was responsible for creating the QA process from scratch to meet the needs of the org. This includes release process, bug formats, triage schedule, test environments, manual, and automated test suites.
Duties Performed
Test Coverage
Projector, being a web-based graphics and presentation SaaS, required a large suite of manual and automated regression tests to verify graphics consistency between builds, prevent regressions, and enforce performance standards.
Leadership
Jeff build the QA team from 0, leaning on years of previous knowledge from other startups and the needs of Projector. He hired QA engineers capable of testing modern graphics software. He also guided and mentored the new hires on the Selenium regression suite.
Creativity
Given that Projector as a product was graphics presentation software, being creative with testing was very important. Jeff spent time thoroughly examining new features and pushing them to their limits, even inspiring new features to be created.
Tools Used
Tooling at Projector was intentional and powerful. Jeff built a test automation framework using WebdriverIO powering Selenium with TypeScript. Given that the product was rendered using WebGL, creative solutions had to be implemented, as Selenium cannot interact with WebGL normally. Jeff worked with the engineering team to add a layer over the canvas(accessibly via flags) that allowed selenium to interact with the WebGL canvas indirectly. Automated image compare libraries were then implemented in the Selenium suite to verify that graphics were consistent between releases with large amount of test data, historical data, and new screenshots.
​
Outside of automation, Jeff administered JIRA for the company, utilized DataDog to view logs and investigate bugs, and chose TestPad as the Test Case Management tool. Given it was a fast-paced and small startup, using a heavier tool like TestRail didn't make sense for the org.