Update: please note that I have since switched to using a set of bash scripts instead of poluting the Git repository with git svn
.
Author: Kaspars Dambis
kaspars.net / @konstruktors
Update: please note that I have since switched to using a set of bash scripts instead of poluting the Git repository with git svn
.
Author: Kaspars Dambis
kaspars.net / @konstruktors
group :production do | |
gem 'unicorn' | |
# Enable gzip compression on heroku, but don't compress images. | |
gem 'heroku-deflater' | |
# Heroku injects it if it's not in there already | |
gem 'rails_12factor' | |
end |
Creating async tests with jasmine is quite intuitive.
If you've read the documentation, then you are aware of the [waitsFor
][2] and [runs
][2] helpers in Jasmine.
I had more than one async action in my test, so it required an inspection on my side to verify that Jasmine would run the test in the same way I had expected.
If you specify a series of waitsFor
or waits
and runs
callbacks, then Jasmine will start the countdown for each waitsFor
at the appropriate time (in this gist - after the previous runs
callback was completed).