Ola Nilsson
Ola Nilsson
This PR is probably older than my maintainership, and as it was marked WIP I never gave it much thought. I don't think I'll get to it soon considering how...
One of the problems with the current way of dealing with tests is that every time you evaluate a `describe`macro, that complete suite with all of its sub-suites and cases...
Have you tried setting `print-circle` to `t` as described by @alphapapa in https://github.com/jorgenschaefer/emacs-buttercup/issues/218#issuecomment-1151658577 ?
It's very possible that `print-level` and `print-length` cuts of before print-circle` in this case. Backtraces obviously need some work.
I think I need to see the info file, because I do not get how this can happen. I do not see how the process of creating the info file...
The search of coverage data actually uses `cov-coverage-file-paths` as the starting point. Unless that has been customized it will start by looking in the current dir for a `.gcov` file,...
So that was a lot of explanation and not a lot of solution. It would be nice to fix the issues described in my last post, but I'm afraid it's...
Just so I do not forget: My idea was, that if I from `/some/project/containing/source.js` find `/some/project/unrelated/lcov.info` and the `SF` entries in that file are relative it should be possible to...
What would `:to-error` do different from `:to-throw`? The name `:to-throw` is unfortunate, it actually checks for signals raised by `signal` and `error`. I'm considering renaming it to `:to-signal`, but maybe...
I've submitted #3175 as a possible solution.