Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

[08:51:59 EDT(-0400)] * anastasiac (n=team@142.150.154.160) has joined #fluid-work
[09:03:02 EDT(-0400)] * michelled (n=team@142.150.154.197) has joined #fluid-work
[10:18:25 EDT(-0400)] * theclown (n=theclown@142.150.154.101) has joined #fluid-work
[10:24:22 EDT(-0400)] * EricDalquist (n=dalquist@bohemia.doit.wisc.edu) has joined #fluid-work
[10:36:16 EDT(-0400)] * colinclark (n=colin@ginger.caret.cam.ac.uk) has joined #fluid-work
[10:36:45 EDT(-0400)] <colinclark> michelled: Having weird problems with IM today. I saw your message about using expect() in our unit tests.
[10:36:49 EDT(-0400)] <colinclark> I think it's a great idea.
[10:37:27 EDT(-0400)] <michelled> great
[10:37:55 EDT(-0400)] <michelled> My only concern with using 'expect' is that it may get annoying if it's breaking because people are working on the test
[10:38:14 EDT(-0400)] <michelled> What I've been doing is writing the test and once I'm happy with it adding the expect statement.
[10:46:44 EDT(-0400)] <colinclark> michelled: Makes sense. I think it's a nice tool for sanity checking. The only problem I've encountered is if you're running tests in separate functions, such that the main test doesn't actually know how many tests will be run. This is probably a sign of a poorly written test, anyway.
[10:48:21 EDT(-0400)] <michelled> colinclark: true, unless there was a way to break up the expects. I'm not sure how it works - I've only been putting in a single expect at the top of a test.
[10:48:53 EDT(-0400)] <colinclark> michelled: I tried once to break up the expects, but it didn't work the way I hoped. Worth looking at more closely when we're not all so focussed on the release and conference prep.
[10:49:22 EDT(-0400)] <michelled> ya
[11:10:46 EDT(-0400)] <anastasiac> Hey, colinclark (and anyone else, I guess)
[11:11:00 EDT(-0400)] <anastasiac> I have a question about how we're supposed to set the 'affects' version in JIRA bugs
[11:11:04 EDT(-0400)] <colinclark> anastasiac: shoot
[11:11:47 EDT(-0400)] <anastasiac> I've just found a bug in Uploader trunk. I don't think it's present in the release 0.3, and I imagine it will be fixed before the actual 0.4 release
[11:11:53 EDT(-0400)] <anastasiac> so what version does it affect?
[11:12:27 EDT(-0400)] <colinclark> anastasiac: Good question.
[11:12:54 EDT(-0400)] <colinclark> Is it present in the beta?
[11:13:03 EDT(-0400)] <anastasiac> it will be, yes
[11:13:40 EDT(-0400)] <colinclark> anastasiac: It wouldn't hurt, since we're releasing it, to create a version for 0.4 beta
[11:13:49 EDT(-0400)] <anastasiac> that makes sense.
[11:14:04 EDT(-0400)] <anastasiac> but for future refernece, suppose we weren't releasing anything? what would we use?
[11:14:15 EDT(-0400)] <anastasiac> should we create a version called "trunk" for these cases?

  • No labels