Ben Willenbring

Abstract: Setup guide intended for QA Engineers unfamiliar with Docker. In early 2019, devops was making a strong push to move toward container-based testing and development. At that time, no one on the QA team was familiar with using Docker. The move away from “bare metal” testing to container-based testing was expected to be a slow, staged transition. Helping our QA team install Docker and get the application up and running quickly was an important first step in making that transition.

Abstract: An incident report detailing the root cause analysis of a subtle regression arising from an optimization my team had worked on, and shipped in one of our major releases. I prepared this report on the heels of fixing the issue and identifying the root cause.

These types of reports are routinely provided by devops when there are service outages/interruptions. This report was the first of its kind prepared by any team outside of devops, and set the standard for how agile teams should handle the documentation of software-only regressions falling outside the scope of devops.

Abstract: A gentle intro for front end developers / QA engineers looking to write UI integration tests for the Shotgun web application. An incremental progression of going from `hello world` to logging in, to page navigation, to running an action menu item in a grid of entities and asserting on the result.

Abstract: Procedural guide for any engineer or customer support person wanting to run a surface regression pass against our cloud-based transcoding service with standardized media hosted on a publicly accessible S3 bucket. While the files in this test do not exhaustively represent what our transcoder supports, they offer a baseline affirmation of functionality (ie: a smoke test validation) that there is nothing glaringly wrong.

Abstract: Provides an overview of what to check for when exposing a new ActiveRecord model as a UI-enabled entity in the Shotgun web application. This document was prepared during feature development of Shotgun’s watermarking service in 2016. At that time, there were quite a few unwanted and undocumented consequences associated with simply turning on an entity model. This documentation was a first attempt at clarifying those consequences.