[Windmill-dev] Negating assertions?
adam at osafoundation.org
Wed Dec 19 11:57:58 PST 2007
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
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.
> 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
>> 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