[Windmill-dev] Negating assertions?

[Adam Christian]

This is one of those things I have been avoiding until a user asked  
about it. Dynamically generating nots for each of  the available  
asserts is probably the best plan. I will put this on my list for the  
next round.

Adam

On Dec 19, 2007, at 11:50 AM, Mikeal Rogers wrote:

> I suggested to adam that he, if possible, dynamically create a "not"  
> namespace inside the waits and asserts namespaces that mirrored the  
> regular assertions with negative assertions.
>
> I don't know if that is doable, but we do need negative asserts and  
> waits for nearly all cases.
>
> -Mikeal
>
> On Dec 19, 2007, at December 19, 200711:10 AM, Robert Leftwich wrote:
>
>> I'm finding that occasionally I want to test that a user cannot do
>> something, e.g. click on a Saturday date in a calendar that should  
>> only
>> let them choose weekdays. I know I can pass 'assertions=False' to the
>> WindmillTestClient constructor but then I have to manually add all  
>> the
>> assertions to the rest of the test.
>>
>> Is there a way to turn off assertions for a single test line or  
>> better
>> still, negate the assertion, so that it is thrown if ['results'] is
>> False rather than True?
>>
>> Robert
>> _______________________________________________
>> Windmill-dev mailing list
>> Windmill-dev at osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/windmill-dev
>
> _______________________________________________
> Windmill-dev mailing list
> Windmill-dev at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/windmill-dev