DEV Community

loading...

Discussion on: Test Angular Components in Storybook

Collapse
anshulnegitc profile image
Anshul Negi

Doesn't it create more work for web-developer as for UI changes we can directly inspect elements on the browser?

Collapse
geromegrignon profile image
Gérôme Grignon

It's not just about inspecting UI changes. You can display a component in complete isolation without having to care how to access it into your application (routing, conditional rendering) and change its inputs on the fly to test different use cases.

Collapse
anshulnegitc profile image
Anshul Negi

Then it would be helpful in scenario where application comes for maintenance or bug tracking.

Thread Thread
integerman profile image
Matt Eland Author

Imagine scenarios where it's hard or slow to get to a particular component or a component in a specific scenario. It actually makes it easier on developers pretty quickly. My experience is that you don't need to do a lot of maintenance on stories you've already created.

Admittedly, though, for the simple text-based game project, 95% of the components are going to be visible on initial app load, so it's a bit of a bad example, but on larger and more complex applications with more navigation and components tucked away in odd corners, it can make a lot more sense.

Thread Thread
anshulnegitc profile image
Anshul Negi

Yeah, need to do more project that requires intense UI then it would be useful to use this tool.