Lin Xu

IMHO, `buttercup` is great for unit tests. Integration tests or any tests that require testing the full stack should not exist in buttercup, but in some "other testing framework". Buttercup...

@codygman the driver code is https://github.com/lastquestion/explain-pause-mode/blob/master/tests/cases/driver.el, but it's not very documented and kind of still early days. Most of it is related to the package under test, the actual code...

> As you know buttercup is modeled on jasmine, not mocha. And I'm not knowledgeable in either of them. So I'll have to look into how that will work in...

Oh, so sorry! I didn't check the documentation carefully enough! And yes, indeed, it does print an error. I expected something like this to work: ```elisp (describe "A suite" (before-all...

Haha, of course, but I really just meant if you were interested in the direction. Hm, my read of subtests is that it is a way to repeat a test...

Hey @shackra !! Two bug reports, I'm so sorry that it's always you :_) But much appreciate for sticking through and trying it out and reporting bugs. ❤️ I wonder...

Wait, @shackra , are you on latest HEAD? I deleted `was-profiled` in the big PR for #42, it doesn't exist anymore. Can you update to HEAD and let me know...

Before #42, it was 100% possible that `explain-pause` would get confused when `server.el` is being used, which it always is used by `magit`, and then it would either think that...

❤️ let me know. I am going to pull a PR together tonight / tomorrow that will give more debugging information when it actually happens as well, it will print...

I will implement a report-error for when profiling does not match expected state and close this issue with it, that way if it happens more I will have sufficient debugging...