Mike Williams wrote:
David Kemp wrote:
we could leave the default behaviour as is, but support both "trim"
and "untrimmed" for those wanting to be explicit about it.
assertValue | foo | untrimmed:tolower:regexp:^fo*$
I'd been thinking that stacked prefixes would be similar to nested
funct
David Kemp wrote:
we could leave the default behaviour as is, but support both "trim"
and "untrimmed" for those wanting to be explicit about it.
assertValue | foo | untrimmed:tolower:regexp:^fo*$
I'd been thinking that stacked prefixes would be similar to nested
functions. From that point o
[EMAIL PROTECTED]
wrote on 19/08/2005 01:20:40 AM:
> On Thu, Aug 18, 2005, Alexander Dvoretskiy wrote:
> >
> >
> > I suggest
> > 1. Remove all the implicit trimming and removeNbsp calls,
> > 2. Add special assertions like assertTrimedText.
> >
>
> Objection! ;-)
>
> HTML output trims space
On Thu, Aug 18, 2005, Alexander Dvoretskiy wrote:
>
> I face difficulties when assert strings with (important for
> indenting) leading spaces. How can I understand from the code
> there is no clear opinion on where to trim strings in tests. For example
> I can't use assertSelection to check stri
Hello,
I face difficulties when assert strings with (important for
indenting) leading spaces. How can I understand from the code
there is no clear opinion on where to trim strings in tests. For example
I can't use assertSelection to check string like
" some text" because expected value is tri
