In some development environments, the ParserTests may always fail with an UnsatisfiedLinkError:
Lars Volker reported seeing this last month, while no others saw this. As of this morning, I started to experience the same issue.
I believe the issue is related to some static loading of classes and/or libraries in Java because changing the ParserTest to initialize the Frontend makes the error go away. I haven't been able to pin-point the exact issue with loading, but it makes sense that the ParserTest should initialize the Frontend static state if it will be called by libfesupport later since it seems to be an issue affecting some environments and not others, i.e. subject to environmental factors.