[Windmill-dev] Negating assertions?

[Mikeal Rogers]

On Dec 19, 2007, at December 19, 20073:50 PM, Adam Christian wrote:

> Okay so for syntax here:
> 	1. asserts.not.assertNode (not sure if this is possible)
> 	2. asserts.notAssertNode
> 	3. asserts.asserNodeNot
> 	4. asserts.!assertNode (not sure if this is possible either)

I'm partial to the namespace, but it's purely because i think it looks  
better.

It may be worth doing the notAssertNode ( or is it assertNotNode? ) to  
have some kind of parity with jsunit, which we do support in the  
JavaScript framework.

>
>
> If the vote is for 1/4 I will research it more in depth. If you can  
> respond asap that would be best as I wanna get this hacked in before  
> I leave for WA tomorrow morning so we can do a 0.3.whatever we are  
> at release.
>
> Adam
>
> On Dec 19, 2007, at 11: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