Actually, I implemented the last one tonight, it took me a bit of time in
notepad ^^ but it does the job, I still have to modify the tests themself
and that, should take me until the end of the week end, I'll be busy this
week.
Now those are valids :
<AssertError value="Error: Le paramètre allowedFormatChars est incorrect. Il
ne doit pas contenir de chiffres." />
<AssertError value="{['ReferenceError: Error #1074:', 'country',
'mx.resources.Locale']}"/>
<AssertError value="{['ReferenceError: Error #1074:']}"/>
<AssertError value="{[]}"/> // pass each time which make sens because it
means contains nulls
<AssertError value=""/> // unchanged
The error message for "contains" looks like: Expected Error contains
"ReferenceError: Error #1074:"..."country"..."mx.resources.Locale", got ....
(the real error)
Any thoughts ?
-----Message d'origine-----
From: Alex Harui
Sent: Monday, November 05, 2012 6:29 PM
To: flex-dev@incubator.apache.org
Subject: Re: About Flex runtime
On 11/4/12 11:35 PM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:
I'm for the last proposal and I was thinking about to create an other
assertion like AssertErrorContains which would take an Array as parameter
to
check the error value against.
Something like <AssertErrorContains value="{['ReferenceError: Error
#1074:',
'variant', 'mx.resources.Locale.']}"/>
I think I would just add a "contains" property to AssertError, we'll
probably have to go touch each one of them anyway. I would lean against
adding a new test step.
Or maybe just change AssertError to do an indexOf instead of == and override
"value" so if it gets an array it do indexOf on the array. Hmm. I like
this one better.
What do you think ?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
