[Windmill-dev] Assert param names

[Adam Christian]

Essentially going from:
{"params": {"validator": "blah", "id": "header"}, "method":  
"asserts.assertText"}

to:
{"params": {"text": "blah", "id": "header"}, "method":  
"asserts.assertText"}

I think it's a bit more intuitive, nicer for code readability, but  
most importantly I think it's what users are used to when switching  
from other test frameworks.

Im not married to the idea, just throwing it out there.

Adam

On Nov 16, 2007, at 3:36 PM, Mikeal Rogers wrote:

> Can you give an example of what the new API call would look like.
>
> -Mikeal
>
> On Nov 16, 2007, at November 16, 20073:23 PM, Adam Christian wrote:
>
>> When I wrote the assert statements I used the word validator for  
>> every method as target to assert, for example:
>>
>> asserts.assertText takes a param validator that is the text that  
>> you are validating, wouldn't it make more sense to have this param  
>> simply called text, and for assertValue have it assert value?
>>
>> I can add some code to make it backwards compatible, but going  
>> forward I think it's more intuitive to call it what it actually is.
>>
>> Adam
>> _______________________________________________
>> Windmill-dev mailing list
>> Windmill-dev at osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/windmill-dev
>