Week no 10 – Bugs Bugs Bugs!

The summit has given me energy to go all in for the automated tests ( also partly that there is only a month left! ). This week was quite engaging. I was working on multiple tests at a time. I filed patches for checking the states of the preferences options and the awesome-bar url check and the favicon check. Also was engrossed on the tests on core functionality of the preferences, as also tests on the tab loading behaviors of the awesome bar.

The one problem I had with writing the patches was the use of window.messageManager. The mobile team would like every tests to use messageManager instead of eventManager and waitFor, for like waiting for events and pages to load. But it is not the case in mine though. I tried using them for page loads, but it does not wait and often the results show fail which it is not. Anyways the guys are working on it, and I have used the other two options for this.

The core functionality tests are the major stumbling block for now. One of the tests to check whether the remember passwords dialog is prompted when the option is switched off. But the problem is that once a textbox is clicked, the form helper loads. After entering a string to it ( password ), it cannot “click” the next element, that is the submit button. Actually it cannot do any clicks on other elements. Anyways I think this issue will be resolved and by the next week I am hoping to see a patch for it done.

The next step would be to work on more tests. I would be concentrating on the preferences options ( checking text and color ), the awesome bar and start work on the download manager. A busy week ahead!

Week no….. ah I lost the track!!!

Yeah, seriously I lost the track on the current week number, all because of the awesome awesome Mozilla Summit 2010. Not only a week that was gone for the summit ( that includes 2 days of flight), but also a week before that because of the visa refusal ( more on that in the coming blog post(s!) ).

So what about the GSoC? Sure, it’s lagging behind, maybe by a week or so. But I got all the things on note and surely be taken care of with few extra hours of work. The best part is that I met my mentor there ( Joel Maher ) and also other people that count like Mark Finkle, Clint Talbert, Gerv, and many others. The summit was a enthralling experience and has only made me more committed to Mozilla, Mozilla ROCKS!!!

So the next few weeks will be tight for sure, with the mid-term evaluation round the corner (July 16). But I am pretty confident that I can pull the things through, that I have got all things in order and now more than ever I know what to do (Pretty strong words eh!). The summit has given me whole bunch of experiences that has enriched my knowledge on the mobile firefox and other related stuff. The discussion with jmaher was great and he turns out to be an amazing guy with tons of experience in the field of automation. I feel so lucky to have him as my mentor and now we are both ready to put things on the fast track and get them done for the benefit of getting the first version of Mobile Firefox into the many phones round the world!

So the next week, I’ll be concentrating on putting new patches for testing the preferences options like the homepage selection, checking the core functionality, and also text and colors. Also I am hoping that I’ll put a patch through for testing the awesome bar favicon and trivial stuff. So that’s the plans for the week and I will be updating the next week.

Oh yeah, for the records, I’ll put this week as week no. 9 as I can find it in the calendar… 🙂

Week no 6 – First Patch through!

Due to unfortunate circumstances, I had to skip off week no. 5 post. Anyways, here I am with the latest updates of what has happened so far in the automation tests for Fennec front end.

The first patch, that was basic panning of preferences pane of Fennec, has undergone a lot of ridiculous changes (which you can see from this bug489158). But finally I found out the way to compare the panning values with that of variables that depend on the Fennec size. This way I got rid of all the hard-coded values except one which has no possible way to find out. After all that and few silly changes Continue reading