dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.1.0
v0n has quit [Ping timeout: 240 seconds]
mpapis has quit [Excess Flood]
michal_papis has joined #cinch
michal_papis is now known as mpapis
gtech has quit [Ping timeout: 240 seconds]
gtech has joined #cinch
leftylin1 has joined #cinch
leftylink has quit [*.net *.split]
Rickmasta has quit [Excess Flood]
Rickmast- has joined #cinch
xeviox|afk has quit [Ping timeout: 240 seconds]
xeviox|afk has joined #cinch
xeviox|afk is now known as xeviox
honkfestival has joined #cinch
<honkfestival> hi all
<honkfestival> what's going on with these two methods? is the FIXME related to why modes isn't part of the known options for a bot configuration?
postmodern has joined #cinch
v0n has joined #cinch
honkfest1val has joined #cinch
xeviox|afk has joined #cinch
honkfestival has quit [Ping timeout: 240 seconds]
xeviox has quit [Ping timeout: 240 seconds]
xeviox|afk is now known as xeviox
honkfest1val is now known as honkfestival
v0n has quit [Ping timeout: 244 seconds]
geopet has joined #cinch
<geopet> Would this be the right place to ask about how to test a gem using Cinch as the API?
<geopet> I'd like to test the functionality of my gem without testing the API that Cinch provides.
<geopet> Is there a good way to abstract that? Or documentation to show me how to do that?
<leftylin1> I have two ideas here
<leftylin1> hmm, well if the gem in question is a Cinch plugin, you could take a look at https://github.com/jayferd/cinch-test
leftylin1 is now known as leftylink
<geopet> Oh! Thank you! That may help with my immediate need.
<leftylink> my other suggestion, if it doesn't is that you can roll your own thing that mocks out most of Cinch's stuff. I did such a thing in https://github.com/caitlin/cinch-coupgame/blob/master/test/coup_game.rb, but it's a lot of stuff and cinch-test is probably easier
<leftylink> and I think cinch-test was probably the better option for that
<leftylink> but in case cinch-test doesn't suit your needs, maybe you can look at that for ideas
<geopet> Thank you so much, leftylink. This is a huge help.
<leftylink> I <3 testing
<geopet> Me too! :) I just didn't want to test Cinch while testing my own stuff. Just isn't necessary. :D
<leftylink> there's *also* running an IRC server on localhost, but that's not usual testing strategy and I hope we don't have to go there
<geopet> Right... It would make testing this a little more brittle because the setup would require a lot of anyone else wanting to run the suite other than me.
<geopet> leftylink: Do you have an example of how cinch-test is used? I think I understand it from the usage docs, but it would be nice to see an additional example.
<leftylink> hmm, I don't have one of my own on hand, but I think https://github.com/jayferd/cinch-test/blob/master/spec/cinch_test_spec.rb can help you out here
<geopet> *nod* I was just reading that. Thank you!
<leftylink> actually, let me throw one of my things on Gist
<leftylink> and maybe catepillar would be amused to see it too... https://gist.github.com/leftylink/9265252
<leftylink> anyway, I post that because it shows the hacktactular lengths to which I go to make it so that even timers can be tested
<leftylink> normally the timer fires every 60 seconds? Nah, I just use crazy j0nx to access the timer and fire it
<leftylink> I dunno how much useful stuff you can extract out of that, but there it is
<geopet> The one useful thing is that it looks like you're building something pretty cool!
Azure has quit [Ping timeout: 240 seconds]
<geopet> But, thank you! I'll read this over and see what I can glean from it. :)
<leftylink> it's for a game I (and catepillar ) play
<leftylink> that takes in data from the game's API and posts various things to IRC
<leftylink> so yeah, that's the motivation there
<geopet> Very nice!
<geopet> leftylink, thank you so much for your help. I need to go afk for the moment, but I really appreciate your time.
<leftylink> my pleasure
<geopet> :)
Azure has joined #cinch
honkfest1val has joined #cinch
<lagweezle> leftylink: also ty from me for the testing stuff; I'm finding similar frustrations as geopet. :)
honkfestival has quit [Remote host closed the connection]
geopet has quit [Ping timeout: 245 seconds]
postmodern has quit [Quit: Leaving]
Azure has quit [Quit: Textual IRC Client: www.textualapp.com]
Azure has joined #cinch
Azure has quit [Client Quit]
honkfest1val is now known as honkfestival
honkfestival has left #cinch [#cinch]
Azure has joined #cinch
postmodern has joined #cinch
kludge` is now known as kludge`_
kludge`_ is now known as kludge`
nickrw has quit [Remote host closed the connection]
nickrw has joined #cinch
postmodern has quit [Quit: Leaving]
v0n has joined #cinch
geopet has joined #cinch
geopet has quit [Ping timeout: 240 seconds]
geopet has joined #cinch
xeviox is now known as xeviox|afk
geopet_ has joined #cinch
geopet has quit [Ping timeout: 270 seconds]
Azure has quit [Quit: My MBP went to sleep.]
Azure has joined #cinch
geopet_ has quit [*.net *.split]
Azure has quit [*.net *.split]
v0n has quit [*.net *.split]
Azure has joined #cinch
Azure has quit [Ping timeout: 240 seconds]
v0n has joined #cinch
Azure has joined #cinch
geopet has joined #cinch
geopet_ has joined #cinch
geopet has quit [Ping timeout: 264 seconds]
geopet_ is now known as geopet
postmodern has joined #cinch
rek2p0wn has quit [Remote host closed the connection]
Netfeed has quit [Ping timeout: 252 seconds]
literal has quit [Ping timeout: 252 seconds]
literal has joined #cinch
v0n has quit [Ping timeout: 240 seconds]
geopet has quit [Ping timeout: 240 seconds]
Azure has quit [*.net *.split]
v0n has joined #cinch
Azure has joined #cinch
Azure has quit [Client Quit]
Azure has joined #cinch
geopet has joined #cinch
Azure has quit [Quit: My MBP went to sleep.]
v1n has joined #cinch
v0n has quit [Ping timeout: 240 seconds]
Azure has joined #cinch
Netfeed has joined #cinch
kith has quit [Read error: Connection reset by peer]
kith has joined #cinch
Azure_ has joined #cinch
Azure has quit [Disconnected by services]
Azure_ is now known as Azure