Closed Bug 795187 Opened 12 years ago Closed 10 years ago

Clearly indicate phone's ID/POOL

Categories

(Testing Graveyard :: Autophone, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mcote, Unassigned)

Details

The IDs autophone uses to identify phones are based on the MAC address and device description from SUTAgent.ini. This is useful from a SUT perspective (MAC address displayed on screen, IP for DeviceManager), but sometimes it's useful to know the phone's serial number, which is generally stored in the POOL SUTAgent.ini setting (though we will almost certainly need both a device ID and a pool ID in the future). We should at least log it in worker log, and maybe in the device status.
Whiteboard: [mentor=mcote][lang=python]
Hi Mark,

I am new and i want to take up this Bug, can you tell me how do i reproduce this bug?
Hi Anil, welcome!  Mark is out on vacation, but bc can help out.
Anil, great to have you on board. I think the first step will be to for you to get Autophone up and running in your local environment.

You will need a rooted android phone or other android device to test your patches. Do you have one available?

How familiar are you with Python and setting up virtual environments? Are you familiar with using source control programs such as git or mercurial?

Autophone is available via git at:
https://github.com/mozilla/autophone/

Autophone Installation instructions are in the repo at:
https://github.com/mozilla/autophone/blob/master/INSTALL.md

I don't think you need worry about running the s1s2 tests or the unit tests initially at least. Getting the smoketest to run and log the appropriate information would be sufficient I believe.

Ping me tomorrow in the #ateam channel on irc.mozilla.org. My nick is bc. If I don't answer right away please wait as it appears we may have considerable differences in time zones. You can also ping Mark Côté  (irc nick mcote). If I'm not immediately available.
Thank you Bob and Clint,

I don't have a rooted android phone. 

I will set the autophone work environment right away.

I rate myself an intermediate in python, though i have not worked well with virtual environments, but it should not be hard to understand. I am familiar working with git.

Hope i can help you guys.
Great. I think we can probably get by with an emulator from the Android SDK.
Hi anil, any luck setting up the emulator?  Need any help?
Hello, I am new too and I am thinking to get started with this (my first bug). I know python and am vaguely familiar with git. Is this bug too tough for newcomers? (because I don't really get the description). But the detailed instructions are motivating. I don't have an android device, could try the emulator.
I think the hardest part would be getting it all set up.  See comment #3 above.  If you can get that working, I'm pretty sure you'll be able to fix this bug. :) Feel free to drop by #ateam on irc.mozilla.org if you need some help/advice.
Whiteboard: [mentor=mcote][lang=python] → [mentor=mcote][lang=python][good first bug]
I don't think this is valuable anymore, since we'll be deprecating phonedash, and we've already changed the way in which we identify phones.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Whiteboard: [mentor=mcote][lang=python][good first bug]
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.