I used PhantomJS to drive a system integration with a hostile legacy web application.
By hostile I mean that the legacy system had no API, was implemented using obfuscated code, and resisted being driven by URLs.
We needed to integrate with it to create documents, calendar appointments, etc. in the legacy system, based on stuff that was happening in the newer system we were building.
We ended up using PhantomJS to implement a module that drove the legacy system via its HTML user interface -- pushing buttons, selecting meeting participants from the HTML select tags, submitting forms, etc.
Although that sounds (and is!) hacky as hell, it worked flawlessly 100% of the time. PhantomJS was a gift from the gods.
Comments
I used PhantomJS to drive a system integration with a hostile legacy web application.
By hostile I mean that the legacy system had no API, was implemented using obfuscated code, and resisted being driven by URLs.
We needed to integrate with it to create documents, calendar appointments, etc. in the legacy system, based on stuff that was happening in the newer system we were building.
We ended up using PhantomJS to implement a module that drove the legacy system via its HTML user interface -- pushing buttons, selecting meeting participants from the HTML select tags, submitting forms, etc.
Although that sounds (and is!) hacky as hell, it worked flawlessly 100% of the time. PhantomJS was a gift from the gods.