OverCoder has quit [Quit: Connection closed for inactivity]
TomyWork has quit [Remote host closed the connection]
seydar has quit [Ping timeout: 240 seconds]
Vonter has quit [Ping timeout: 248 seconds]
Vonter has joined #ruby
seydar has joined #ruby
brw has joined #ruby
brw has quit [Client Quit]
yziquel has joined #ruby
brw has joined #ruby
hiyori has quit [Quit: Client closed]
brokkoli_origin has quit [Remote host closed the connection]
brokkoli_origin has joined #ruby
Vonter has quit [Ping timeout: 245 seconds]
Vonter has joined #ruby
brokkoli_origin has quit [Ping timeout: 240 seconds]
brokkoli_origin has joined #ruby
desnudopenguino has joined #ruby
alphacentauri has quit [Quit: WeeChat 4.0.5]
alphacentauri has joined #ruby
patrick has quit [Killed (NickServ (GHOST command used by podge!~patrick@fsf/member/patrick))]
patrick_ has joined #ruby
patrick_ is now known as patrick
yziquel has quit [Quit: Ping timeout (120 seconds)]
blop has quit [Ping timeout: 252 seconds]
blop has joined #ruby
<impomatic>
Thanks @ox1eef_
brokkoli_origin has quit [Ping timeout: 258 seconds]
brokkoli_origin has joined #ruby
_ht has joined #ruby
<desnudopenguino>
anyone have any good articles on writing tests for roda based sites?
<desnudopenguino>
there are so many different testing gems i have no idea where to even start
<ox1eef_>
rack-test is probably a good start.
<desnudopenguino>
thanks!
<ox1eef_>
Last time I used it was with test-unit, and it worked well. 'include Rack::Test::Methods', define an 'app' method that returns the Rack application, get "/foo" to make a GET request, and assert against last_response.
<desnudopenguino>
cool thanks! that should help get me rolling. it's been a while since i've done any testing in ruby stuff
crespire has quit [Killed (NickServ (GHOST command used by crespire1!~crespire@user/crespire))]
crespire1 has joined #ruby
<seydar>
i'm excited to use async for non-blocking I/O
<seydar>
for parallelism with CPU-bound threads, i've been using the parallel gem, which marshall's the data and sends it to the child processes
<seydar>
when i look at the child processes in `top`, they all have the same memory footprint as the parent process. is that just an accounting trick, or is that true? the memory footprint is significantly higher than i would expect
shokohsc510812 has joined #ruby
shokohsc51081 has quit [Ping timeout: 240 seconds]
shokohsc510812 is now known as shokohsc51081
<leftylink>
I can never remember the order of args to File.write. I always have to check
<adam12>
desnudopenguino: I use capybara and rack-test.
_ht has quit [Quit: _ht]
<desnudopenguino>
adam12: ok. cool. i have some doc reading to do now
m_antis has joined #ruby
m_antis has quit [Client Quit]
<ox1eef_>
I do remember some oddities around the response body with rack-test. In the test environment, it is a StringIO object, and in the real world it is some type of proxy object that's just not the same. That was with Rack3.
gr33n7007h has quit [Quit: WeeChat 4.0.4]
gr33n7007h has joined #ruby
infinityfye has quit [Quit: Leaving]
ruby[bot] has quit [Remote host closed the connection]