Fix test fixture patching and move all fixture to json #107
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Most fixture data should be defined in "test/fixtures.json", with its data used
to set the default firebase data for a test.
Your tests should reset the firebase before running, using
test/utils.js#setFirebaseData(somePatchToBaseData)
. e.g:To retrieve fixture data, you can use
test/utils.js#fixtures(somePath)
; e.g.:Returned values cannot be corrupted by a previous test and will always reflect
the data set in "tests/fixtures.json".
You can use
test/utils.js#auth
to authenticate with one of the fixtureregistered users:
auth.admin
(admin);auth.chris
alias forauth.admin
;auth.alice
(premium, can create event and has an "alice-event" event setup);auth.bob
(participant of "alice-event" event);auth.emma
(only registered - to test non-participant access to event).They can used with targaryen tests:
Thoses object cannot be corrupted by previous tests.