As in any development effort, good engineering practices, including code reviews, group design discussions, and adequate research, are imperative. Writing and maintaining a parser is an expensive project that should not be undertaken without complete support from development and upper management. Source code access, even if read only, is crucial. Developers should be alerted to coding practices that will break test automation, and they should be reminded of the link between design for testability and speedy bug reporting. Automation engineers who learn and exploit existing development build processes and tools will fare better than those who attempt to work in isolation.
Numerous possibilities exist for further study and development.
Data might be assembled comparing the time invested in writing and maintaining the parser to the decrease in time required to detect and report bugs. Internationalization engineers might modify existing parsing code slightly and implement a working version of their own with a relatively small investment. The benefits of the parser are abundant, as is the work involved in its development and use. Levine, John R., Tony Mason, and Doug Brown. Perry, Paul, et al.