How to update, test library component for breakage before publishing?

Wanting to know if anyone has a successful strategy for making updates to components in a library and then testing them to avoid breaking designs using those components? Example: Button components - updating elements inside button, publishing and the entire team loses any button label override, how do you avoid or test for that?

I have noticed breakage on library components after only very minor design changes when published in regards to overrides resetting.

Or is there any good documentation around what does and doesn’t break a component?

Hi @Toby_Magrath1

This is not the solution, but it’s how we do stuff at my company and so far it worked :

  1. When we want to create/edit a component of our design system. We open a new branch and start working on this component in this new branch.
  2. As it’s done, we asked each other to review it, in order to make sure it’s release proof (kinda QA test : resizing it, overflowing the text, …)
  3. Once reviewed we publish the component (only for our Figma team) and then we jump into a test file that have all component in it, with variations, on some mock-up situation so when we update a component we can see if its change actually break our design or not.
  4. If it breaks, go back to step 1, if not we release it to everyone

I’m afraid there is no such things as the documentation your mentioned.

Hope it helped

1 Like

Thanks @Haroll appreciate the tips. I also watched this video and tried out that process on some component updates today, it worked and I was able to switch the library to test out a couple large use components to make sure there was no breakage prior to merging the branch and republishing from the main library.

@Haroll Hey, I’ve noticed your reply and pretty much do the same thing. I know it’s been a while since you’ve posted this, but I’m just wondering though, When you publish to your team, how do you publish to the organisation afterwards when everything looks good?

In Figma when I publish to team and then afterwards try to publish to the org, I don’t see the changes anymore (presumably because I already have them). So theres basically “nothing” to publish anymore.

The video posted above feels like a silly workaround. I should be able to publish to my (design system) team for testing and then publish to the organisation afterwards as a way of testing, no?

You should but as far as I know there isn’t a way to do that built into Figma. That video is literally from Figma so if there was I guess they wouldn’t have made that video, althought it is 2 years old. If you find a way inside Figma let me know!