Influence of Acceptance test settings on unitTest
Closed this issue · 4 comments
config.action_controller.allow_forgery_protection must be true in order to work with sessions for the acceptance tests. But i causes that ~60 unitTest fails.
Currently config.action_controller.allow_forgery_protection = false so we should either
- enable it for all acceptance tests or
- disable it for all non acceptance tests
this could be done with by using the acceptance test flag:
config.around(:each, :acceptance_test => true) do |ex|
relates to the Conversation on the commit:
222a1c6#commitcomment-9564748
okay, so setting config in spec_helper doesnt work out.
I now created a new environment which is executed after the test environment. That works fine, but now travis isnt loading the seed file correctly... :/
juhuuuuuuuuu!
https://travis-ci.org/hpi-swt2/event-und-raumplanung/builds/49436435
ready to merge :)
Finished in 11.68 seconds (files took 4.92 seconds to load)
9 examples, 0 failures
Finished in 1 minute 26.99 seconds (files took 5.33 seconds to load)
626 examples, 0 failures, 11 pending
fyi: @DasDingGehtNicht
werent there 16 tests? i mean i had 9 tests passing too ;)
yea but they were excluded => true due to the point that they point to current user stories in Sprint 4 :)