Android ADB could get stuck

The adb itself is a nice tool and it came up with a nice feature to block itself until the emulator is up:

adb wait-for-device - block until device is online

However, this feature is not well implemented by Google:


Note that this command does not cause adb to wait until the entire system is fully booted. For that reason, you should not prepend it to other commands that require a fully booted system. As an example, the install requires the Android package manager, which is available only after the system is fully booted.


Another issue with this comment is that it could get stuck occasionally due to a bug in either emulator or adb.

June's first post

I am surprised to find out that I did not do much blogging in the month of May. At least I made a status report to Hassen and Jan. Time to write this chapter.

Time to be active on blogging and writing of industry experiment

It looks that the TDD project begins to slow down. There were less development activities in last 2-3 weeks in the TDD project. Interestingly, non-TDD is still active.

Summary of weekly telemetry report

Parameters:
Project: The-NON-TDD-Project
Week: 11-Mark-2007 to 17-Mar-2007 ~ 22-Apr-2007 to 28-Apr-2007
Report : TDDProject-Member-Report

The development slows down too in the month of April. It looks like the TLD developers tested somewhat less than the TDD group. It is a pity that the percentage of TDD is not up to the point.

Anyhow, it is interesting to see this difference.

Summary of weekly telemetry report

Parameters:
Project: The-TDD-Project
Week: 11-Mark-2007 to 17-Mar-2007 ~ 22-Apr-2007 to 28-Apr-2007
Report : TDDProject-Member-Report

Starting of April, the development slows down a bit observed from this chart. The effort spent on test is about a quarter of the effort spent on production code. It is interesting to know that developers never stopped working on tests. :-)

The length of episodes varies from 11 minutes to 41 minutes in this period. There is no pattern found yet.

The percents of TDD by time and number are both small. A thorough review of development method is necessary in order to tailor Zorro's rules for them, or they could do TDD better.

Test Last Project did not catch up tests yet

Test first project did not write enough test in the previous post, the test last project is even worse. Test must be forgotten by developers.

Production and Test DevTime

This picture is the telemetry stream of Total, Production, and Test development time of the test first project. Apparently the TestDevTime is significant lower than the time spent on production code in weeks 1, 3, and 4. More time was spent on test in the week 2.