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
{{ message }}
This repository has been archived by the owner on Jan 13, 2022. It is now read-only.
Cross-posting from chenglou/node-huxley#30
The node version has a jasmine-like xname option to temporarily disable some tests. I'm also considering dropping it and opt instead for >name instead, which allows you to run a single test.
Below is the part I didn't know. Seems like the best setup would use one huxleyfile per component, and glob them all into one update run. Then you could record one ui component at a time, which is the common case. Thanks for referencing #30!
Maybe I should make this stand out more in hux -h, but you pass the folders containing the huxleyfiles, aka without the /Huxleyfile.json part.
Btw, you can also use globs. And multiple globs =). Huxley will dedupe the paths correctly.
The docs recommend dedicated urls and single component testing. It would be clearer to describe that you can (and should) have multiple huxleyfiles, in that same section, otherwise you run into issue #48 :)
The documentation section you referenced (sumarized):
Create a dedicated test URL for Huxley to hit that uses mocking.
Test a small unit of functionality.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there a way to record a new test without re-recording old ones?
If I add a test to
Huxleyfile.json
, it seems like I have to re-record all of the tests.I have been working around this by:
hux -r
enter
to skip tests I've already recordedIs there a huxlified way to do this?
The text was updated successfully, but these errors were encountered: