Re: [O] FAILED test-org-clock/clocktable
Hi Achim, Achim Gratz writes: > As nice as org-test-with-temp-text is, it is really hard to figure out > what happened if there's an error — would it be possible to make a > (named) buffer with the result if the test is unsuccessful, at least as > an option? I explored ert a bit for this and found the `ert--test-buffers' variable... but I'm not sure how we could store info from this into a file. -- Bastien
Re: [O] FAILED test-org-clock/clocktable
Achim Gratz writes: > The last test will fail if run before 15:00... either the clock table code > gets > smarter to recognize that you'd want the end of the day when specifying ":tend > " or the test should specify ":tend ". I've pushed a fix (29117be) for this issue after checking the documentation again and running the tests manually to really see what happened. As nice as org-test-with-temp-text is, it is really hard to figure out what happened if there's an error — would it be possible to make a (named) buffer with the result if the test is unsuccessful, at least as an option? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
[O] FAILED test-org-clock/clocktable
The last test will fail if run before 15:00... either the clock table code gets smarter to recognize that you'd want the end of the day when specifying ":tend " or the test should specify ":tend ". Regards, Achim.
