-
Notifications
You must be signed in to change notification settings - Fork 54
Chromatic QA checks with different storybook knob values #1673
Comments
We should see about disabling the default story on the chromatic runs and look to add a few more stories with the service value hardcoded for running against chromaticqa |
@jroebu14 proposed a better solution to just hardcoding all the values:
|
@oluoluoxenfree and I were looking into automatically creating RTL variants of stories. We found it's possible but not with the current input provider set up that sets the default service of a story. I've created an issue for this that I think should be fixed if we were to continue with the approach in #2366 The other option is to manually create RTL variants for every story which could be time consuming and error prone. |
@jroebu14 & @oluoluoxenfree I think what you are working on in #2366 is the better solution, especially as most of what the input provider did was us was pulled out a while back. |
Is your feature request related to a problem? Please describe.
Currently, Chromatic QA checks just the standard set of props in Storybook.
For examples such as the Consent Banner, the standard is using the
news
service. e.g. ?path=/story/consentbanner--defaultIt does not carry out tests against a service such as
arabic
, which has a different layout. It should be testing this variant as well.https://www.chromaticqa.com/component?appId=5d28eb5ee163f6002046d6fb&name=Components%7CConsentBanner&mode=interactive&buildNumber=289
![Screen Shot consent banner chromatic QA](https://user-images.githubusercontent.com/3028997/62638031-8ad28080-b934-11e9-8f46-3d6885e9877a.png)
Describe the solution you'd like
There should be automated tests that check different variants of Storybook examples.
Describe alternatives you've considered
Updating our stories, so we have a separate url for each variant. e.g. ConsentBanner RTL & ConsentBanner LTR.
Testing notes
[Tester to complete]
Dev insight: Will Cypress tests be required or are unit tests sufficient? Will there be any potential regression? etc
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: