Concluding workweek,Santi and Iheaded to London for a two day JSON Wire Protocol shop at the Mozilla London office. We be join by Simon Stewart of Facebook and the Selenium Project, David Burns of Mozilla, François Reynaud of ios-driver, and Dominik Dary of Selendroid. The workshop could not have hap without the leadership of the Selenium Project, and we ’ re excited to be working closely with them to farther promote and promote the goal of developing lasting standards for peregrine automation. The Selenium Project was subservient in germinate standards for web mechanisation with the W3C, and as mobile automation and frameworks continue to evolve, we all agree it ’ s all-important to develop standard specifications for how nomadic mechanization should work and secure maximum interoperability between frameworks. We experience that the workshop was a huge success that fostered meaningful collaboration between projects for the benefit of users and the open source community. We believe collaboration like this will aid mobile automation move forward.

What we covered

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

We made great progress over the two days of the shop in planning what the specs of a standardized mobile automation protocol would look like and developing a roadmap of how to get there. You can read the agenda of the shophere, and see detailed bit of what we coveredhere. On day 1 we did detailed spec preparation, work out areas where the different projects didn ’ t align and coming to a consensus about how to move forward. Day 2 focused on developing roadmaps for submitting extensions to W3C and enforce change in the automation servers and client libraries. The end end of all this planning is to eventually subject proposed measure specs for the JSON Wire Protocol to the W3C, simply as Selenium has do for browser mechanisation.

What this means for peregrine mechanisation

We hope that the work we ’ ve done thus far and the work to come will ultimately greatly benefit anyone doing mobile automation, as well as the open source community. It means that users will be able to switch between mobile automation model as demand without ask to relearn how each work, creating a more robust unfastened rootage mobile automation ecosystem. We hope greater interoperability will facilitate grow an already grow unfastened source community that can provide great community support for people appear to do mobile automation, and yield people the security from seller lock-in that open origin can provide.

Products

Global creature

Set up and mix

Resources

Company