Javascript + PhantomJS testing

[wikimatze]

This sounds very interesting, I could work on it in a separate branch and contact you how to work with it. What do you think?

[fgarcia]

I must seriously review my Github notifications, just saw your issue!

PhantomJS was in my list, but before I was planning this:

• clean up the classic Rack::Test example (no rspec)
• mount a Sinatra based application for API
• some async/ajax Javascript operation on the demo

Maybe that will ease your example. In any case, the asynchronous response is a common problem when doing Javascript.

Regarding testing, I value being independent for each gem, but certainly I could write many posts related with the opinions I show in this project

[wikimatze]

I sometimes miss the notifications too. I will wait, until you are finished with your tasks.

[fgarcia]

@wikimatze it seems like I will do a more dramatic move towards Javascript than expected. I will notify you when I am also ready with #2

[wikimatze]

Saw your #2 report and I still want to play around phantomjs - even with managing all the JavaScript related things with grunt.

[fgarcia]

@wikimatze I am done with my structure refactoring and prepared an app that focuses on testing with capybara+rspec (pademo-testing).

also there is one simple feature at '/tester/test1' where an ajax request takes some seconds to load a text. That should be perfect to show phantomjs

However if you still want to do that part, you should wait until next Padrino release or use now the current 'master' since there is a bug that will not allow the gems to be mounted alone from the rest.

padrino/padrino-framework#1747