<    March 2017    >
Su Mo Tu We Th Fr Sa  
          1  2  3  4  
 5  6  7  8  9 10 11  
12 13 14 15 16 17 18  
19 20 21 22 23 24 25  
26 27 28 29 30 31
01:06 ixti joined
01:06 <ixti> Hi all
01:07 <ixti> did anyone encountered an issue with `super(**kwargs)` in rspec?
01:11 <ixti> oops.. it's issue with my code (seems like)
03:46 TheWhip joined
04:25 TheWhip joined
05:30 TheWhip joined
05:55 Sp4rKy joined
06:03 TheWhip joined
06:30 bronson joined
07:16 tvw joined
07:20 Sp4rKy joined
07:22 zpe joined
08:04 raphink joined
08:04 raphink joined
08:41 tvw joined
10:20 zpe joined
11:46 byteflame joined
11:46 byteflam1 joined
12:01 User458764 joined
12:40 zpe joined
13:45 zpe joined
14:06 byteflam1 joined
14:35 Karunamon left
16:24 byteflam1 joined
16:26 byteflame joined
16:28 zpe joined
17:07 raphink joined
17:07 raphink joined
18:27 raphink joined
18:27 raphink joined
18:44 tvw joined
18:55 zpe joined
18:56 zpe joined
19:34 zpe joined
20:15 netzfisch joined
20:51 rakm joined
20:52 <rakm> hey! i have a method that raises an exception on bad input. the method writes something to a file. I already have a unit test that tests that an exception is raised. How do I write another unit test that makes sure that nothing is written to the file?
20:52 <rakm> in other worse, how do I handle an exception in a test, without setting an expectation for it using expect {}.to raise_error
20:55 <rakm> I can add a rescue to the test, but that seems meh
20:56 <rakm> `expect(mock_open_file).not_to receive(:write); subject.download rescue false`
21:02 rakm joined
21:21 raphink joined
21:21 raphink joined
22:08 raphink joined
22:08 raphink joined
22:19 netzfisch joined
22:26 netzfisch joined