Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Karma Tests #110

Open
CWSpear opened this issue Apr 28, 2015 · 1 comment
Open

Karma Tests #110

CWSpear opened this issue Apr 28, 2015 · 1 comment
Assignees
Labels
Milestone

Comments

@CWSpear
Copy link
Collaborator

CWSpear commented Apr 28, 2015

As part of #69, I want to set up some Karma tests so once quirks are found, we can create some tests to make sure we don't regress later. These would be in addition to Acceptance Tests for cross browser quirks, but easier to write, maintain and run, and will check for our core features.

One example is I remember special care was taken to get button groups to work when hovering over other buttons then moving onto the button with a dropdown.

The real problem here: I'm not sure we can really test this with anything less than an Acceptance Test.

I'm open to suggestions in general about how this testing can help us, if at all.

@CWSpear CWSpear added this to the v3.0 milestone Apr 28, 2015
@CWSpear CWSpear added the ready label Apr 28, 2015
@CWSpear
Copy link
Collaborator Author

CWSpear commented Apr 28, 2015

If we use a combination of touchstart/touchend events around mouseenter/mouseleave events to decide how to handle opening the nav, then these kinds of tests could help her.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants