When working on front-end tickets, do you usually take screenshots or record the current look of the website before making changes? For instance, if you modify the UI and submit a pull request, do you share visuals of the new design so your teammates can easily see it without switching to your branch?
4 Answers
It really depends on the size of the change. For smaller tweaks, I usually skip it, but for larger UI updates, I definitely take screenshots to help my team understand the modifications.
I think it's a bit unnecessary. Even for minor changes, I prefer to check out the PR myself and see how it looks across different devices and test for any edge cases. I’d need to run the dev environment anyway.
If that were my workflow, I wouldn’t survive! That's more of a QA task. Developers should focus on the code, not just the resolutions.
I always take before-and-after screenshots for UI changes. It speeds up the PR review process and cuts down on the back-and-forth. I add them right in the PR description. Smaller teams can get away with just using screenshots, but some use tools like Percy or Chromatic for automated visual comparisons.
It all depends on the situation, but make sure to spell everything out clearly. Communication in tickets or with the wider team shouldn’t sound like casual texts.
We used to rely on that too, but then we introduced dev previews, and it’s been a total game changer! I haven’t had to check out a PR in ages.