[Issue 11783] Make std.datetime unittesting faster

d-bugmail at puremagic.com d-bugmail at puremagic.com
Sun Dec 22 05:05:38 PST 2013


https://d.puremagic.com/issues/show_bug.cgi?id=11783



--- Comment #10 from Jonathan M Davis <jmdavisProg at gmx.com> 2013-12-22 05:05:31 PST ---
FYI. I just tried commenting out all of the assertThrown unit tests in
std.datetime, and the running time on my machine went from nearly 24 seconds to
just under 4. So, while the other tests definitely need to be refactored and
optimized (in which case, they'd take even less time), the ones that throw
exceptions currently take up about 5/6th of the running time (and take up a far
smaller portion than that of the total tests). So, optimizing those tests is
definitely low hanging fruit.

If you'd like, since I do have a few days off for Christmas and can spend at
least a little bit of time on D, I can spend some time over the next few days
strategically disabling tests in order to improve how long std.datetime's tests
take without losing a lot of tests, and then I can go back and refactor them
properly in a month or two when I finally have time to focus on that. So, you'd
get faster execution times but poorer testing in the short term, and then for
the long term, I can sort out how to get good execution times without losing a
lot of testing.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------


More information about the Digitalmars-d-bugs mailing list