My thought was that automated testing properties would be a separate bead. That way you can more easily rip it out before going to production.
My 2 cents, -Alex On 1/13/17, 5:53 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Hi, > >I am currently writing some unit-tests for the Examples and encountered >something I would like to discuss with you. >For example, in FlexJSStore the search field doesn’t have an id so it is >not very simple to select the field. I could simply give the field an id, >but I remembered in the old Flex there were “automationName” attributes >which elements could have. These names helped identifying elements during >tests. What do you think if we should start supporting some attributes >that help writing tests (This would also be something that other >frameworks don’t have and that could be treated as quite handy). > >Chris
