Lunchtime conversation w/a principal web dev:

Him: "I think we need Tugboat at work."
Me: "Oh? Tell me more about that."
Him: "Yeah, I've made and merged like 3 PRs today, but my co-worker on this project can't easily review them."
Me: "Why is that?"

1/6
Him: "Well, we only have one QA server, and we're only supposed to deploy the entire release when it's ready. Not parts of it. So I don't have anyplace I can put these PRs for review. There's also a dev environment, but everyone deploys there, so stuff gets blown away."

2/6
Me: "What do you envision happening if you had a place to deploy PRs?"
Him: "Well, the QA team could start doing review a *lot* sooner instead of waiting for the release at the end of the sprint. Also, my co-worker would have someplace to do manual testing and code review."

3/6
Me: "What does manual testing and code review look like for your team?"
Him: "Well, we write manual testing steps in the instructions for every pull request, but our local databases don't contain any real data, so we can't really do effective testing on our locals."

4/6
Him: "We have a process to create data for manual testing, but it's such a PITA and involves so many steps that we basically never do it. So if we had an environment for every PR, with real production data, we could test effectively during code review & QA better/earlier."

5/6
Me: "Yup, basically everything you've just described are exactly the problems Tugboat was created to solve. Sounds like you need Tugboat at work."

Deploy Previews for every PR... there are so many good reasons to include this in your #webdev process!

6/6
You can follow @tugboatqa.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:

By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.