More and more do even small software systems rely on one or several external services (not under the control of the same team or even organization). Historically, these services would often be interacted with via web-scraping techniques, which are naturally very fragile. Recently, APIs based on (typically) HTTP and JSON are becoming more and more common, but are often defined very informally (with little or no explicit documentation) and change frequently and without announcement.
As a result, the consuming system will often break at unexpected times and in surprising ways and no amount of testing can avoid this.
This workshop will discuss techniques used by the consumers of such services to make the situation more bearable, for example:
The workshop will use a discussion-heavy format: Two presentations (of 10 minutes each) will be followed by 20 minutes of discussion; plus a break after every two such packs (every 80 minutes).
Submit papers of up to 6 pages length, in IEEE conference format, as PDF. If you are a practitioner, you may also submit merely an outline of your presentation (of around 500 words) in no particular formatting or a slide deck (30 slides maximum).
Submit via Easychair.Take subway line U3 to Dahlem Dorf, then 400m on foot.