03:04
<kke>
anyone got cruisecontrol.rb working with padrino projects?
04:07
<repo-commit>
[padrino-framework] DAddYE pushed 2 new commits to master: http://git.io/8s6EpA
04:07
<repo-commit>
[padrino-framework/master] Fix some remaining issues when generating an admin app using a custom model - David A. Cuadrado
04:07
<repo-commit>
[padrino-framework/master] Merge pull request #794 from dcu/master - Davide D'Agostino
04:12
<travis-ci>
[travis-ci] padrino/padrino-framework#291 (master - be5759e : Davide D'Agostino): The build was fixed.
04:12
<travis-ci>
[travis-ci] Change view : https://github.com/padrino/padrino-framework/compare/711bb69...be5759e
04:12
<travis-ci>
[travis-ci] Build details : http://travis-ci.org/padrino/padrino-framework/builds/749572
09:04
<kke>
gave up with cruise, got heidi working without any hassle
09:38
<diago>
I'm having an issue spec'ing a model that is using AppName.deliver, does anyone know if this should work ok?
09:38
<diago>
the test bombs here: https://github.com/padrino/padrino-framework/blob/master/padrino-mailer/lib/padrino-mailer/helpers.rb#L112
09:39
<kke>
diago: i have after_create do { AppName.deliver(:foo) } and it works ok
09:39
<diago>
I keep getting: NoMethodError: undefined method `messages' for nil:NilClass
09:40
<diago>
messages from what I can tell is coming form the line above
09:40
<diago>
It works fine in dev || production
09:41
<diago>
kke: Do you have a unit test or spec for it?
09:42
<kke>
only cucumber step with mock proxy at_least(1)
09:43
<diago>
hm , ok. I'm using minitest atm
09:46
<diago>
kke: How do you deal with database buildup and teardown when using cucumber?
09:46
<diago>
I spec everything out without the db, but the controllers rely heavily on it
09:51
<kke>
using db_cleaner
09:51
<kke>
Before do DbCleaner.start and After do |scenario| DbCleaner.truncate or something, just copypasted from db_cleaner's readme
09:58
<diago>
kke: yeah, I used to use it. I guess I'll go back to using capybara for controller tests
10:03
<kke>
diago: yeah initially we decided to ditch unit tests and just do functionals and have some unit test kind of stuff in the steps like "Then /the user should be admin of the company/ do @company.has_role?(:admin, @user).should be_true end"
10:03
<kke>
not sure how that's going to work out later on
10:04
<kke>
but doing unit tests on models seems like being much re-testing the ORM
10:04
<diago>
I like to go true BDD but it is time consumming
10:04
<kke>
i think it has speeded up the development for me
10:05
<diago>
kke: we unit test all the business logic
10:07
<kke>
"tests pass, good enough for now, next scenario" instead of getting stuck in finetuning the details and exceptions and stuff
10:26
<diago>
kke: how do you generate the urls for get in your tests?
10:26
<diago>
like AppName.url( :base, :index )
10:26
<diago>
this doesn't give /app_name/base/index
10:26
<diago>
it leaves off the app_name
10:30
<kke>
diago: not using AppName, just "visit url_for(:companies, :show, :id => @company._id)", but i don't have any url prefix in my app so maybe it's different for you
10:32
<diago>
hmm, yeah we have about 5 apps
10:32
<diago>
I'll try it though
11:02
<diago>
kke: non of the helpers are working form within the specs
11:02
<diago>
I keep having to do App.url_for but then the internal redirects do not work after that
11:25
<diago>
jesus, I have no idea what it is doing
11:56
<diago>
so padrino rake routes, AppName.url_for, and test all create different routes...
11:57
<diago>
what the hell
18:13
<krawek>
hey guys, do you know how does the mountable apps impact the performance?