End-to-end tests with Cypress

[sapegin]

Right now we only have unit test and very simple test that check bundles for JS errors in headless Chrome. But we don’t know that Styleguidist is actually usable.

Cypress seems like a good choice.

• [x] Setup Cypress
• [x] Write first test
• [x] Move cypress folder to test folder
• [ ] Write more tests:
  • [ ] Open a component in isolated mode (should show 1 component), go back (show show all components again)
  • [ ] Open an example in isolated mode (should show 1 example of 1 component), go back (show show all components with all examples again)
  • [ ] Click on a component in the sidebar should scroll to this component
  • [ ] Typing in the search field in the sidebar should filter components in the table of contents (same for sections names)

[glebez]

It feels that we can check off first two boxes. And think on breaking the third one into more actionable, i.e. 'write cypress tests for sidebar', since some core test are already in place.

[sapegin]

I’ve added a few — feel free to suggest more 🦄

[haquezameer]

@sapegin @glebez I would like to take this up if it is still open.

[sapegin]

@haquezameer Awesome! I'm sure most of the todo items weren't done yet.

[haquezameer]

ok @sapegin. I am taking this up.

[dhuang612]

is this available to work on?

Thanks

[sapegin]

@dhuang612 sure, there's never too many tests.

[milafreckled]

Hi, I was inspired by this issue, and already made a pull request with some tests, you can check and correct me if necessary. I think it must cover all unchecked boxes above.

[gulammoyuddin]

is it still available to work on?

[SivalakshmiViswanathan]

I would like to contribute. Is it still available?