Comments (3)
Hello, and thanks for the idea! I have thought about this in the past, but I am quite unsure about it. For anything but :to-throw
, you really want to see the evaluated value as well. You can always get the original expression by looking at the source, but you have no way of knowing the resulting value.
So you'd end up with a pretty unwieldy error message for most cases.
I agree the situation for :to-throw
is not exactly good, though. Maybe #41 can improve that somehow? I'm open for ideas.
Btw, let me know if that's too much feedback in too little time! buttercup is really fun to work with, congratulations on this neat project :)
Thank you for the kind words! I'm of the opinion that it should always be ok to create issues. I might delay answering to some of them, though :-)
from emacs-buttercup.
To take an example, if I do: (expect (+ 1 1) :to-equal 3)
, then the failure message is Expected 2 to `equal' 3
. What I would like to see is something more like Expected `(+ 1 1)' to `equal' 3 but it was 2 instead
. That message has the original expression, the expected value, and the observed value.
from emacs-buttercup.
I've written some code to implement this in #93.
from emacs-buttercup.
Related Issues (20)
- Failing specs triggers complete backtrace
- Tests fail after updating buttercup HOT 11
- Trace formatting takes ages (with mutual refs?) HOT 4
- More interactive commands HOT 4
- Backtraces print byte code instead of original expression for byte compiled tests HOT 1
- Buttercup gets stuck if :var not defined at beginning of body HOT 1
- Breaks with latest changes to format-spec HOT 2
- Too strict argument check in `buttercup--enclosed-expr` HOT 5
- Interactive testing ergonomics HOT 3
- Bizarre failure to match error signal message with :to-throw HOT 6
- How to properly run all tests in a current buffer without using markdown with list code blocks? HOT 3
- Native compilation problem when spying on certain primitives, such as file-exists-p HOT 4
- package autoload is obsolete
- spy-on test fails with native-compilation HOT 1
- New failures with native-compilation on emacs-next-minimal-30.0.50-1.9d27b95 HOT 2
- Don't look inside functions HOT 2
- 1.33 -> 1.34 update causes hangs in GNU Emacs >=30.0.50 (git) HOT 8
- buttercup issue with 1.34 change to use open closures on Emacs 29 HOT 12
- Respect NO_COLOR
- No traceback when asserting within a lambda? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from emacs-buttercup.