Mobile Automation Deep Dive Meeting Wed Apr 17, 1PM PST
Today is our third mobile automation "deep dive" meetings, where we
discuss in-depth an aspect of mobile automated testing for FirefoxOS and
Firefox for Android. The idea is to both expand the common base of
knowledge on the state of the art in this area (as we continue to add
new mobile test harnesses, frameworks, and platforms to the mix) as well
as come up with plans/ideas which could help us in the future.
This time the topic is the logging output of our harnesses. We have
quite a few intermittent failures on Android and B2G in our production
infrastructure that are -- debugging the root causes of these problems
is not easy. Is there anything we could be displaying that would help us
narrow these problems down? On the other end of things, is there some
redundant information that's getting in the way of understanding what's
really going on?