On a second look, it looks like GeneralFunctionsTest is causing the error.
It changes the resourceStringFunction, but does not set it back to the default
one. (although I’m not sure why not — it should be changed back in the finally
block).
On Jan 8, 2015, at 10:56 AM, Harbs <harbs.li...@gmail.com> wrote:
> Try changing:
> GlobalSettings.resourceStringFunction("invalidReplaceTextPositions”)
> to:
> GlobalSettings.defaultResourceStringFunction("invalidReplaceTextPositions”)
>
> The resourceStringFunction can be overridden, and true overridden function
> might not be returning the correct text. My “solution” is probably more of a
> hack, because I think these error strings might be localized somewhere, but
> I’m not sure about that.
>
> On Jan 7, 2015, at 11:29 PM, piotrz <piotrzarzyck...@gmail.com> wrote:
>
>> Hi,
>>
>> I have removed "Ignore" tag from the test "spanElementReplaceTextInvalidPos"
>> -> ElementOperationTest.
>> There is something interesting happening there which might not be exactly
>> related to the TLF.
>>
>> We have this part of code.
>>
>> https://paste.apache.org/44I4
>>
>> It's failing because it do not find text "your" in the span - Which is
>> good. In method "replaceText" we have following code.
>>
>> https://paste.apache.org/d2Hw
>>
>> It is basically throwing an error which we are expecting, but
>> GlobalSettings.resourceStringFunction do not return any text for
>> "invalidReplaceTextPositions".
>>
>> Could we have some bug in that area ?
>>
>> Piotr
>>
>>
>>
>> -----
>> Apache Flex PMC
>> piotrzarzyck...@gmail.com
>> --
>> View this message in context:
>> http://apache-flex-development.2333347.n4.nabble.com/Unit-tests-in-TLF-tp36199p44215.html
>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
