Tyler Hill

I write tests for a living. The test itself is the easy part.

Got started at Microsoft testing Halo and Gears of War. Testing video games is not nearly as fun as playing them, but I learned a lot, mostly how to break things.

Since then, my work has covered a fair amount of ground. Web UI and cross-browser automation at Smilebox. Hardware and software integration at Peloton, where the device under test occasionally was a treadmill. Web and Test Ops at Committee for Children. Retail and e-commerce systems at Rhino and lululemon. iOS automation at Fieldwire, which makes construction management software for people working on actual job sites.

Wherever I land, the questions are usually the same: what tests should actually be running, when should they run, and can we trust the results? The third one is almost always the hardest.

Like everyone else right now, I'm trying to figure out what AI can genuinely do in a testing workflow. Some of it is quite useful. I'm still not sure if it'll replace me, help me, kill me, or none of the above, but I'm paying attention.

Outside of work: seeing live theater with my family, pickleball, musical things here and there, and an unwavering loyalty to Seattle sports teams. When the Seahawks lose I'm in a bad mood. I'm working on that.