[09:38] yeah I gave up and went back to a lucid container :P [09:40] :P [09:44] Things seem to be a lot smoother with a fresh late-Precise-generated Lucid container [16:02] hi [16:03] hi alexh [16:03] any hints on why the bug activity API returns an empty entries set but a non-zero total_size? [16:03] e.g. https://api.launchpad.net/1.0/bugs/123920/activity [16:03] <_mup_> Bug #123920: Bluetooth Logitech Dinovo Keyboard/Mouse don't work < https://launchpad.net/bugs/123920 > [16:05] happens with every bug I've tried, not just that one, fwiw [18:53] Is there a make harness that lets me do doctest stuff? [18:57] (or, what do I import to get that stuff?) === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [19:22] Laney: what do you mean? [19:26] I'm trying to make a doctest and it'd be good to be able to test this interactively [19:26] but I don't know what to import into the harness repl to get those functions [19:26] it doesn't really matter; I'm feeling it out without this. [19:29] ah [19:30] so we consider doctests one step up from the spawn of evil [19:30] you might like to not make one [19:30] yeah? [19:30] I thought they were the way to test UI changes [19:30] yah [19:30] very much deprecated [19:30] having testable *documentation* is still good, and if you are writing docs you expect folk to read, feel free to make them a doctest [19:31] but such are not replacements for unit tests or integration tests [19:48] Laney: unfortunately the codebase is not always a good indicator of modern practice :-/ [19:49] another approach is: make your test fast enough that instead of running things interactively in a harness, you can just repeatedly run the test [19:50] cjwatson: I don't know how to test the UI then :P (unless I am misusing the terminology and interactive tests are something different from doctests) [19:51] the reason I want to use the harness is because I don't really have a view of the test interfaces yet so it's most efficient to just be able to bash on stuff [19:51] fyi, the file I am proposing to edit is lib/lp/soyuz/stories/soyuz/xx-distributionsourcepackagerelease-pages.txt [19:51] doctests are noninteractive [19:52] the repl-style tests I mean [19:52] well, anything you can do in that can be recast as a unit test fairly straightforwardly [19:53] just a matter of learning the various self.assert* helpers [19:53] indeed. I just thought these were the way that UI tests were done. [20:05] so a UI test could mean: [20:05] - JS tests [20:05] - html content checking [20:05] - non-ajax form checking [20:05] - ajax integration test [20:06] perhaps a better question is, what change are you making ? [20:06] also, morning all [20:06] bbiab, shopping run [22:22] lifeless: did you see http://cortesi.github.com/pathod/ [22:23] no, looking [22:23] nice [22:23] fault injection test server. woot. [22:25] nice - 200@100k,ascii_letters [22:34] alexh: You're unauthenticated.