You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: