Closed
Bug 795375
Opened 12 years ago
Closed 9 years ago
Report actual fennec version, not the one we are trying to test
Categories
(Testing Graveyard :: Autophone, defect)
Testing Graveyard
Autophone
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mcote, Unassigned, Mentored)
Details
(Whiteboard: [lang=python])
Right now we download build X, install it, run the s1s2 test, and include build X in the results. However, in the event that we somehow failed to install a new build, we might actually be testing an old build. The tests should report the *actual* build version, not just the one we think we're using.
Reporter | ||
Updated•12 years ago
|
Whiteboard: [mentor=mcote][lang=python]
Reporter | ||
Comment 1•11 years ago
|
||
There are a few ways to do this, but one way is to run dumpsys and search for "Package [org.mozilla.fennec]": Package [org.mozilla.fennec] (4064e610): userId=10056 gids=[] sharedUser=SharedUserSetting{40638a28 org.mozilla.fennec.sharedID/10056} pkg=Package{408d7780 org.mozilla.fennec} codePath=/data/app/org.mozilla.fennec-2.apk resourcePath=/data/app/org.mozilla.fennec-2.apk nativeLibraryPath=/data/data/org.mozilla.fennec/lib versionCode=2013011903 versionName=21.0a1 dataDir=/data/data/org.mozilla.fennec targetSdk=14 supportsScreens=[medium, large, xlarge, resizeable, anyDensity] timeStamp=2013-01-20 00:48:40 firstInstallTime=2012-09-15 01:38:10 lastUpdateTime=2013-01-20 00:48:44 signatures=PackageSignatures{406283b8 [406291e0]} permissionsFixed=true haveGids=true pkgFlags=0x0 installStatus=1 enabled=0 It appears that the build ID is stored as "versionCode".
Reporter | ||
Comment 2•11 years ago
|
||
In addition, right now we erroneously refer to all builds as opt. We should glean this from the downloaded build. Probably should be the responsibility of BuildCache.
Assignee | ||
Updated•10 years ago
|
Mentor: mcote
Whiteboard: [mentor=mcote][lang=python] → [lang=python]
Hi Mark. I'm new to bugzilla and would ideally like to start contributing. I'd like to work on this bug if its still active, but would first need some assistance getting set-up and running. Any help would be much appreciated. Thanks.
Reporter | ||
Comment 4•10 years ago
|
||
Hi James, thanks for your interest! Autophone has actually changed a lot recently, and I'm not sure if this bug is still relevant. I'll have to investigate a bit. However, there are other bugs in Autophone, like bug 1037059, that might be suitable. They aren't small, but they shouldn't be terribly complicated either. Regardless, if this project interests you, your first step would be to install the Android SDK (http://developer.android.com/sdk/index.html), which you would need to run Autophone. The next step is to install Autophone itself. See the project page (https://wiki.mozilla.org/Auto-tools/Projects/AutoPhone) for general details, and the INSTALL.md file in the source code (https://github.com/mozilla/autophone/). If you need a hand, probably best to email me or join irc.mozilla.org in the #ateam channel and ask me (mcote) or bc (autophone developer) for help.
Reporter | ||
Comment 5•9 years ago
|
||
bc, do you think this is in any way relevant any more?
Flags: needinfo?(bob)
Comment 6•9 years ago
|
||
I don't think so. If we need to make improvements, I'd rather we start fresh from the current state. -> WONTFIX.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(bob)
Resolution: --- → WONTFIX
Updated•2 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•