Hello Philipp,
Yep, had the same idea just yesterday. But how to keep the trunk also
in a good-consistent shape (if it needs to be kept in a good shape)?
Sunday, July 15, 2007, 3:07:17 PM, you wrote:
> Adam Groszer wrote:
>> Did something at /repos/Zope3/branches/adamg-mechanize-update/,
>> the
Benji York wrote:
It'd be nice to have a -C option that disables -c for when your test
runner has -c included in the default options (as I intend to do with mine).
I've added such an option. The -C switch makes sense, but I'm not
entirely happy with the --no-color version of the name, any sug
Marius Gedminas wrote:
On Sat, Jul 14, 2007 at 03:30:22PM -0400, Benji York wrote:
Digression: syntax highlighting the diffs helps immensely.
Check out
http://svn.zope.org/zope.testing/branches/colorized-output/
I'm very much looking forward to that branch being merged to t
Marius Gedminas wrote:
On Sun, Jul 15, 2007 at 10:44:35AM -0400, Benji York wrote:
I'm doing some work with doctest right now, and am considering how to
make assertions about HTML/XML better.
Fixing https://bugs.launchpad.net/zope3/+bug/126169 would make my life
easier.
I wonder if that beha
On Sun, Jul 15, 2007 at 10:44:35AM -0400, Benji York wrote:
> I'm doing some work with doctest right now, and am considering how to
> make assertions about HTML/XML better.
Fixing https://bugs.launchpad.net/zope3/+bug/126169 would make my life
easier.
Marius Gedminas
--
Microsoft -- because God
On Sun, Jul 15, 2007 at 08:34:43AM -0400, Stephan Richter wrote:
> On Saturday 14 July 2007 04:24, Marius Gedminas wrote:
> > - API documentation: human readability is the primary concern, doctests
> > are in there just to make sure the documentation stays up to date.
> > These are .txt fil
Stephan Richter wrote:
I would not like that. I really, really like to use XPath to select an element
in the HTML structure. The method above would still require me to write
I think I miscommunicated. Let me combine your example and mine to
demonstrate what I was talking about. Say you have
On Sunday 15 July 2007 10:44, Benji York wrote:
> > Right, z3c.etestbrowser does this already. I wish they would have done
> > this with a different object altogether, but they extended the
> > TestBrowser class. But then I do not have enough objectstion to write a
> > new package.
>
> Perhaps some
Stephan Richter wrote:
On Saturday 14 July 2007 15:30, Benji York wrote:
Yep, assertions about HTML (or XML) are difficult to do with plain text.
One option is to feed browser.contents to your favorite HTML (XML)
parser.
Right, z3c.etestbrowser does this already. I wish they would have done
Adam Groszer wrote:
Did something at /repos/Zope3/branches/adamg-mechanize-update/,
the biggest problems seems to be now, that ClientForm won't work in a
subfolder.
Any objections against putting it back to /src?
It won't really matter much, I think, because the trunk of the Zope3
tree will u
On Saturday 14 July 2007 04:24, Marius Gedminas wrote:
> - API documentation: human readability is the primary concern, doctests
> are in there just to make sure the documentation stays up to date.
> These are .txt files.
I disagree. API reference should be automatically created. Text file
On Saturday 14 July 2007 15:30, Benji York wrote:
> Marius Gedminas wrote:
> > - Functional tests: these are .txt files that use zope.testbrowser and
> > are the hardest to debug. There ought to be a better way to make
> > assertions about HTML output than using ELLIPSIS and then pulling
On Saturday 14 July 2007 18:13, Marius Gedminas wrote:
> > > http://svn.zope.org/zope.testing/branches/colorized-output/
> >
> > I'm very much looking forward to that branch being merged to the trunk.
>
> Merged.
Yipee!
Regards,
Stephan
--
Stephan Richter
CBU Physics & Chemistry (B.S.) /
13 matches
Mail list logo
