As I said in previous blogs, I am helping a team that is developing a multi-media product for cell phones. Our continuous integration step involves updating the code, running the tests, testing the application in an emulator, committing the changes and announcing.
Yesterday, we decided to explore a new GUI framework called J2MEPolish. We liked the framework and began using it. After integrating the new framework, we performed all the steps of continuous integration and it ran well. So, we all slept well last night.
Today, we tried running the application on Nokia 6280. It crashed immediately. We all agreed that the step of deployment on a real phone was missing in our continuous integration loop.
In the second edition of Extreme Programming Explained, Kent Beck mentions the following about Continuous integration:
“Integrate and build a complete product. If the goal is to burn a CD, burn a CD….Continuous integration should be complete enough that the eventual first deployment of the system is no big deal.”
The problem is that, the step of installing on the phone is a manual process. Now, if only, we can automate this step, we will do it more often. To install the application on the phone, we have to start the Nokia PC Suite, then start the Nokia midlet installer, then activate infrared and then install the midlet on the phone.
The bright side is that we have resolved to deploy the application manually on a real phone at least twice a day.
Tags: No Comments
0 responses so far ↓
There are no comments yet...Kick things off by filling out the form below.