peteretep

Activity Graph

Page 1 of 1

2019-06-18

[05:36:12] peteretep: Ping timeout: 252 seconds
[05:37:47] peteretep: has joined #ruby

2019-05-31

[12:25:50] peteretep: Ping timeout: 252 seconds

2019-05-13

[12:58:59] peteretep: Ping timeout: 250 seconds
[13:14:49] peteretep: has joined #ruby

2019-05-12

[01:43:16] peteretep: Ping timeout: 264 seconds
[01:45:13] peteretep: has joined #ruby

2019-04-13

[16:50:05] peteretep: *.net *.split

2019-02-12

[00:59:33] peteretep: has joined #ruby

2019-02-11

[23:46:52] peteretep: *.net *.split

2018-12-04

[08:00:51] peteretep: has joined #ruby

2018-07-26

2018-07-23

[15:19:21] peteretep: Ping timeout: 256 seconds
[15:22:06] peteretep: has joined #ruby

2018-07-20

[00:07:21] peteretep: *.net *.split
[00:15:46] peteretep: has joined #ruby

2018-06-20

[03:51:09] peteretep: Ping timeout: 276 seconds
[06:23:07] peteretep: has joined #ruby

2018-06-01

[03:44:47] peteretep: *.net *.split
[07:47:36] peteretep: has joined #ruby

2018-05-29

[02:47:14] peteretep: *.net *.split
[02:48:01] peteretep: has joined #ruby

2018-05-19

[15:33:50] peteretep: Remote host closed the connection
[15:37:53] peteretep: has joined #ruby

2018-05-06

[11:34:08] peteretep: has joined #ruby

2018-04-25

[12:25:52] peteretep: *.net *.split
[12:27:27] peteretep: has joined #ruby
[15:01:23] peteretep: *.net *.split
[15:03:11] peteretep: has joined #ruby

2018-03-02

[05:00:58] peteretep: has joined #ruby

2018-02-28

[23:23:52] peteretep: Ping timeout: 260 seconds
[23:25:23] peteretep: has joined #ruby
[23:25:34] peteretep: Max SendQ exceeded
[23:25:51] peteretep: has joined #ruby
[23:26:06] peteretep: Max SendQ exceeded
[23:26:29] peteretep: has joined #ruby
[23:26:41] peteretep: Max SendQ exceeded
[23:26:59] peteretep: has joined #ruby
[23:27:15] peteretep: Max SendQ exceeded
[23:27:34] peteretep: has joined #ruby
[23:27:50] peteretep: Max SendQ exceeded
[23:28:10] peteretep: has joined #ruby

2018-02-09

[22:41:24] peteretep: has joined #ruby

2018-02-08

[19:25:02] peteretep: Ping timeout: 276 seconds
[19:27:24] peteretep: has joined #ruby

2018-01-22

[15:40:48] peteretep: *.net *.split
[15:41:02] peteretep: has joined #ruby

2017-12-27

[19:13:35] peteretep: Ping timeout: 255 seconds
[19:43:56] peteretep: has joined #ruby

2017-12-21

[06:26:11] peteretep: *.net *.split
[06:31:49] peteretep: has joined #ruby
[06:48:31] peteretep: *.net *.split
[07:24:40] peteretep: has joined #ruby

2017-12-09

[05:06:11] peteretep: *.net *.split
[05:39:53] peteretep: has joined #ruby

2017-12-08

[07:07:04] peteretep: Read error: Connection reset by peer
[07:07:22] peteretep: has joined #ruby

2017-12-07

[14:48:32] peteretep: *.net *.split
[14:55:11] peteretep: has joined #ruby

2017-10-06

[02:12:38] peteretep: Read error: Connection reset by peer

2017-09-21

[21:48:12] peteretep: Ping timeout: 252 seconds
[21:51:09] peteretep: has joined #ruby

2017-09-18

[10:37:55] peteretep: has joined #ruby

2017-07-16

[03:59:51] peteretep: Remote host closed the connection
[22:20:55] peteretep: has joined #ruby

2017-06-20

[00:17:37] peteretep: *.net *.split
[00:22:56] peteretep: has joined #ruby

2017-06-19

[18:19:40] peteretep: *.net *.split

2017-06-17

[18:48:50] peteretep: *.net *.split
[18:49:16] peteretep: has joined #ruby

2017-06-07

[21:29:24] peteretep: Ping timeout: 240 seconds

2017-05-11

[15:33:51] peteretep: has joined #ruby

2017-04-13

[15:10:50] peteretep: *.net *.split
[16:32:06] peteretep: Ping timeout: 252 seconds

2017-04-04

[05:14:23] peteretep: *.net *.split

2017-03-27

[19:37:53] peteretep: Ping timeout: 255 seconds
[19:38:12] peteretep: has joined #ruby

2016-07-25

[08:09:07] peteretep: Here's the article I was working on which was the reason I was asking so many dumb-ass questions about testing: http://www.writemoretests.com/2016/07/perl-python-and-ruby-the-anatomy-of-a-testing-assertion.html

2016-07-19

[07:53:57] peteretep: Are there other common ways - other than `rake test` to run a test suite made up of say RSpec and Test::Unit tests?
[08:03:07] peteretep: I guess my question really is: "Do people always rely on `rake` to run their test suites" and the answer seems to mostly be yes
[08:04:21] peteretep: Do you do that in Jenkins, too?
[08:04:27] peteretep: eg shell out to that as part of your build?
[08:06:13] peteretep: Man, Ruby is weird
[08:07:16] peteretep: ACTION is writing a comparative piece about Ruby/Python/Perl testing
[08:08:33] peteretep: I think there's this heirachy of Python -> Perl -> Ruby, where people think "there are some cool features in that language, but it's being used by KIDS"
[08:08:50] peteretep: Python is dull as all shit, but largely sensible
[08:09:01] peteretep: Perl has some cool features but encourages people to be less sensible
[08:09:10] peteretep: Ruby has some cooler features still, but WTF.
[08:09:41] peteretep: Well the fact that there are 4 or 5 completely uninteroperable testing libraries
[08:10:03] peteretep: Python and Perl testing libraries put a large focus on interoperability
[08:10:54] peteretep: At its most basic level, let's say you've written a testing assertion that looks at - say - Levenstein distance between two strings
[08:11:05] peteretep: And you can say "If differences are > 5 then fail"
[08:11:16] peteretep: But you've also written some sensible debug stuff for it
[08:11:28] peteretep: In Ruby, you then have to integrate that assertion differently in to each testing library
[08:12:07] peteretep: in Perl, you'd get Test::Differences::Levenstein and Perl's Cucumber library would be able to use it, Perl's Capybara equivalent would be able to use it, Perl's RSpec library would be able to use it, Perl's xUnit library would be able to use it
[08:12:48] peteretep: You could run a test suite using the whole thing with the single unified test runner, and get the output as JUnit or HTML or anything else
[08:12:57] peteretep: Python is almost the same
[08:13:43] peteretep: That's what I mean by interoperable
[08:14:17] peteretep: What do you think the 2 are?
[08:14:42] peteretep: Why wouldn't you include test-unit?
[08:16:07] peteretep: Is bacon compatible with other RSpec tools?
[08:16:41] peteretep: Let's say you've written a nice test summary tool that outputs HTML
[08:16:53] peteretep: If you want to use it with bacon, you have to write a special adaptor
[08:17:14] peteretep: You say "of course", but that's not true for Python and Perl
[08:17:22] peteretep: Which is my point :-)
[08:17:51] peteretep: manveru: yep
[08:18:15] peteretep: dminuoso: I suspect that ship has sailed, and there's too much code written to make it feasible
[08:19:13] peteretep: Anyway, that's the Ruby WTF I had in mind :)
[08:20:04] peteretep: What I have discovered is across all three languages, most developers don't really know how their testing tools work
[08:20:21] peteretep: And also don't have any visibility of how the testing tools in other languages work
[08:20:33] peteretep: Which makes this a great basis for my MSc project :D
[08:21:41] peteretep: The core team who added and removed test-unit like 10 times in the last 10 years? :D
[08:22:55] peteretep: ACTION is going from http://www.slideshare.net/kou/rubykaigi-2015
[08:23:04] peteretep: Perhaps it's wrong
[08:26:16] peteretep: the source I gave claims it was then removed again
[08:26:22] peteretep: but whatever

2016-07-14

[13:32:58] peteretep: has joined #ruby
[13:33:31] peteretep: Do all of Ruby's testing tools basically just raise errors on failure?
[13:35:07] peteretep: It seems that Test::Unit's assertions, and Spec::Expectations, they just `raise` to signal an assertion failure
[13:35:18] peteretep: I'm guessing this is the standard Ruby mechanism?
[13:38:29] peteretep: As one example, yes
[13:41:54] peteretep: It would seem there's no sensible interoperability mechanism between these libraries
[13:42:05] peteretep: They all use their own exception classes
[13:44:15] peteretep: If I wanted to use something like hashdiff, I'd have to write library-specific glue for each testing library I wanted to use it with
[13:45:45] peteretep: And impossible to interoperate between different test libraries