[Windmill-dev] Negating assertions?
mikeal at osafoundation.org
Wed Dec 19 17:08:24 PST 2007
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
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
> 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.
> 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
>> let them choose weekdays. I know I can pass 'assertions=False' to the
>> WindmillTestClient constructor but then I have to manually add all
>> assertions to the rest of the test.
>> Is there a way to turn off assertions for a single test line or
>> still, negate the assertion, so that it is thrown if ['results'] is
>> False rather than True?
>> Windmill-dev mailing list
>> Windmill-dev at osafoundation.org
> Windmill-dev mailing list
> Windmill-dev at osafoundation.org
More information about the Windmill-dev