padrino / padrino-integration

Integration testing for the Padrino Framework
www.padrinorb.com
10 stars 4 forks source link

Improve test coverage #4

Open DAddYE opened 13 years ago

DAddYE commented 13 years ago

1) Create a new model 2) Create the admin page 3) Create the frontend page

@nesquena, @achiu any other idea?

nesquena commented 13 years ago

Can we test development reloading, i think so. Creating a controller and model and visiting the controller and checking data is installed. Creating two subapps and testing that session data can be passed between them in a freshly generated project

DAddYE commented 13 years ago

Let's go @nesquena start to improve it ;)

nesquena commented 13 years ago

Yep I plan to start adding more tests to this, as we all should as time permits.

nesquena commented 13 years ago

More ideas, let's have a sinatra app with module included (helpers) and then make sure for every template engine that rendering a template with a partial works.

DAddYE commented 13 years ago

@nesquena extend this: https://github.com/padrino/single-apps then we can add test for every thing ;)

DAddYE commented 13 years ago

Now tests are more more fast.

Now tests are in rspec for a better output and log backtrace

Added spec for single-apps, @nesquena @achiu ? Can we daily improve our coverage? Requires no more than 10 minutes write few lines.

DAddYE commented 13 years ago

I forgot a big mention! Now every thing use our internal padrino reloader, I think there is no way better than this to check that every thing works like a charm!

nesquena commented 13 years ago

Awesome, great work man!

dariocravero commented 11 years ago

See padrino/padrino-framework#920.

wikimatze commented 8 years ago

Can we delete this repository? Integration testing is done on travis.