The JA langpack tests seem to be broken my Labriola's fix for FLEX-34320. The new logic around setting the hasFieldName and hadPreviousFieldName changed and is no longer trigging the expected error which lets the code continue and trigger this new error.
Mike, your thoughts on the logic? The test sets up two SortFields and a compare function on the Sort (not the SortFields) then calls findItem. The first SortField's field name is a non-existent field. I think the old logic would see if the field existed in the data item. The new logic seems to assume the fieldName exists as long as there is no SortField compare function and skips the check if the field exists in the data. -Alex On 5/27/14 12:27 PM, "Alex Harui" <aha...@adobe.com> wrote: >These particular tests are setup up with a try/catch block to trap a >different error but end up trapping this one instead. > >-Alex > >On 5/27/14 8:51 AM, "Justin Mclean" <jus...@classsoftware.com> wrote: > >>Hi, >> >>Looking at the flash log on running the test I can see this error - not >>sure why I don;t get this if I manually run the test via the code. >> >>Error #1063: Argument count mismatch on runtimeErrorTests/cmpFn(). >>Expected 2, got 3. >> >>Any one have a n idea why this may be the case? >> >>Thanks, >>Justin >
