Ensure VTA panel opens when clicking "run tests" button in warning state

[ghengeveld]

As discussed below, rather than hiding the "run tests" button when there's an issue, make sure that it opens the Visual Tests panel. Currently this doesn't work when on a docs page, as there is no addons panel in this situation.

[shilman]

I'd argue this is a conversion feature. Possibly annoying to users but good for discoverability.

[ghengeveld]

This is the current state of the button while onboarding:

After logging in:

I agree with @shilman that this is okay for discoverability. The VTA addon is focussed when clicking the button (unless you're on a docs page).

However, I did also encounter this issue, which happens when restarting Storybook after the initial setup in a monorepo:

The configuration file that's generated currently does not automatically include any of the suggested configuration fixes. I think we should fix that, so the autogenerated config file includes those suggestions.

[MichaelArestad]

I am on the fence with this one. I see it as potentially an avenue for discoverability, but we may want to change from a tooltipNote to something this actionable. For example, we could possibly show a full tooltipMessage with a button that either takes the user through the login flow or takes the user to the addon panel project selection.

[shilman]

@ghengeveld can you elaborate on the config problem and the fix?

I like this button for discoverability, and I agree with @MichaelArestad that we could make it a better experience for helping users get to the next step.

I only worry about prematurely optimizing this flow, so I'd like to:

1. Track the click when it's in this state
2. Do the simplest thing that makes it less frustrating, like possibly what you're suggesting @ghengeveld

Then we can look at the numbers and add the full improvement later if it's worth it. WDYT?

[ghengeveld]

The config issue has been addressed in #306, so this is no longer a problem out of the box.

I'm going to keep the button state as-is, for sake of discoverability. I would hate for the VTA to go unnoticed because it's not configured / the user isn't signed in. The dot isn't obtrusive so even if people leave it like that it doesn't get in the way.

The button already opens the VTA panel, which then contains more details about the problem (or simply prompts for what it needs). I don't think a more elaborate tooltip is worthwhile.

Here's what I'll do (as part of this ticket):

• Make sure that clicking the button opens the VTA, i.e. switch to the next/first story when on a docs page.
• Add telemetry for the click.