trying to fix the py.saunter output

[Adam Goucher]

The hardest part about framework design? Communicating with users.
Things work well.. until you start using something other than plain old
asserts (like say all the things in
https://github.com/Element-34/py.saunter/blob/master/saunter/matchers.py).
I think I may actually have a working example locally that reports
things back, all the things back, to the user when something fails.

Anyhow, https://gist.github.com/adamgoucher/5624886 is up for comment
largely because what I wanted to release today isn't finished upstream
from me and so I'm showing that I am working on this...

SaunterPHP doesn't have the equivalent Matchers class. Yet. (Sooner if
someone wants to sponsor its creation...)

-adam

[Mary Ann May-Pumphrey]

Does the output have to be in the format it is shown in on github? It's very hard to read, and with the possibility of several Verification Failures per test, I don't see it working very well for us.

--mam-p

---

From: Adam Goucher <ad...@goucher.ca>
To: sau...@googlegroups.com
Sent: Tuesday, May 21, 2013 7:50 PM
Subject: trying to fix the py.saunter output

--
You received this message because you are subscribed to the Google Groups "Saunter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to saunter+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Adam Goucher]

Yes. The output is heavily limited by what Py.Test and Python provide and this is already likely into the 'black magic voodoo' territory since I need to look at the call stack and then walk backwards through it to get the calling information. I have one or two more tricks to try, but there is a possibility there is a non-small possibility that this is the best you will get.