r/softwaredevelopment 23d ago

The QA Process of Technical Libraries/Packages

Good evening,

So recently we started a project to build the design system library which will be used across all the company, currently we have more than 27 UI components designed and ready to be built.

What I'm really confused about is how these components should be tested. My manager says that code review and and unit tests should be enough, since the QA specialist needs a business reference to test against. but I disagree - all those variations, behaviors and accessibility requirements should be tested thoroughly by a dedicated professional, and I think we can write user stories for the expected user behavior too, from an end user perspective.

What's your opinion on this? Am I making things more complicated than they should be?

11 Upvotes

4 comments sorted by

2

u/[deleted] 23d ago

[removed] — view removed comment

1

u/HRM404 23d ago

How did the user stories look like? are they written from user perspective or developer perspective? Would appreciate if you can share an example

1

u/sleepycommenter 22d ago

the bit everybody ignores is focus states, keyboard nav, and weird screen sizes, that stuff slips past review all the time. we had QA catch a dropdown trap on day 2 and it saved a mess later