Changes

Jump to: navigation, search

QA SoftVision Team/Mobile

13,338 bytes removed, 14:07, 16 July 2015
Fennec
** Run Appthwack - API 11
** Results RC
 
= Fennec =
== First Steps ==
*A document about Application, Features and ramp up steps can be found [https://docs.google.com/viewer?a=v&pid=explorer&chrome=true&srcid=0BwbEknPON8vbYjAzYmRlZWItYjJkNy00NDk1LWFmYWYtYTJmYTMyMjY4ZWQ5&hl=ro here]
*There are 4 channels for our builds:
***More info about channels [http://mozilla.github.com/process-releases/draft/development_overview/ process releases]; [http://blog.mozilla.com/channels/2011/05/11/merge-dates-vs-release-dates/ merge dates vs release dates]; [http://blog.mozilla.com/channels/category/rapid-release-process/ rapid release process]
[[Image:FaviconNightly.png|32px]] [[Image:FaviconAurora.png|32px]] [[Image:FennecBeta.png|32px]] [[Image:FennecFirefox.png|32px]]
** Nightly : [http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android-r7/ build link]
** Aurora : [http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-aurora-android-r7/ build link]
** Beta : [http://ftp.mozilla.org/pub/mozilla.org/mobile/candidates/ build link]
** Release : [http://ftp.mozilla.org/pub/mozilla.org/mobile/releases/ build link]
 
== Tasks ==
=== Test Creation and Execution ===
====Test Execution ====
* Workflow:
** Step 1: Choose the build you wanna test. Download and install it.
*** If you have previously installed the application, please uninstall it or make an update.
**** Update: Go to about:fennec -> Press Check for updates. Download and install it.(Normally, a notification should appear when a new build is available)
**** Uninstall:Go to home screen for you phone -> Press Menu button -> Settings -> Applications -> Nightly/Aurora/ Firefox Beta/ Firefox -> Uninstall
** Step 2: Go to [www.litmus.mozilla.org Litmus ] (make an account if you don't have one). Choose which of the test you wanna make (the test runs depend on the build you have installed).
*** For Firefox 4 and Firefox 5 please use: Fennec 2.0 Catch-All Test Run
*** For Firefox 6 : Fennec 6.0 Catch-All Test Run
** Step 3: Choose the type of the tests. There are 4 types:
*** Smoketests
*** BFTs - Basic Functional Tests
*** OS Integration Tests
*** FFTs - Full Functional Tests
** Step 4: Run tests and submit your results.
*Results can be found [https://wiki.mozilla.org/QA/Fennec/Waverley#Results here]
 
==== Test Creation ====
* For several bugs, after the fix is made, is required to make test cases
 
=== Reporting Bugs ===
* Please go to : [https://bugzilla.mozilla.org/ BMO] and create an account.
* When a new issue appears first look for already posted bugs. ([http://www.youtube.com/watch?v=14W-XguG--U&feature=related Quick Search Demo] )If you do not find one on your problem, please choose platform and enter the founded bug.
* First rule of thumb. enable USB Debugging on your phone first.Aaron wrote a QMO document on android logging.
** See http://quality.mozilla.org/docs/mobile-firefox/fennec-on-android-logging-with-the-android-debug-bridge-and-logcat/
* To get screenshots, you''ll need to setup DDMS (Dalvik Debug Monitor Service) to capture the images through the tool.Various software out there has this ability.
** http://www.addictivetips.com/mobile/how-to-take-screenshots-of-android-device/
 
=== Performance ===
 
* '''Performance testing using the Zippity Add-on (for old XUL Fennec)'''<br>&nbsp;<br>
** This kind of tests include: Fennec start up Time (Record startup time from cold start to home page ,Record startup time after restarting after applying an addon ) Pageload time (Pick 10 top US sites and record pageload times , Pick 10 top International sites and record pageload times , PR 1.2 vs. PR 1.3 ), Measure Memory Usage (Process Manager App) ( Record memory size at startup (home page only, Open 5 tabs and record memory size , Play an Ogg video and record memory size , Launch a news RSS feed and record memory size , Close Fennec and record memory size)
** For further details please see: [https://wiki.mozilla.org/QA/Fennec/PerformanceBenchmark Performance Benchmark]
** It is used the [http://zippityserver.appspot.com/addon Test Harness extension]
** Requested settings
*** Page load manifest: http://people.mozilla.com/~atrain/mobile/qa_topsites.json (old link http://aaronmt.com/fennec/testing/pageload/qa_topsites.json)
*** Page Load cycles = 3
*** User Key = qa
*** Data Server: default shown
** Results :the submitted results and your average testrun for that device will appear on the [http://zippityserver.appspot.com/graph zippity graph]. Filter by "QA Tp" and you'll see the results you just posted.
** [https://wiki.mozilla.org/index.php?title=QA_SoftVision_Team/Mobile/PerformanceComparison_1 comparison (2010.09.30)]
 
* '''Performance testing via SDK'''<br>&nbsp;<br>
** This automated test records the start-up time not just for Fennec, but even for other browser apps like: Stock Android browser, Opera Mobile, Dolphin HD etc.<br>
** Requested settings:
*** Install the Android SDK starter package from [http://developer.android.com/sdk/index.html here]
**** When Android SDK Manager window is opened, select and install only the Tools package from the [http://farm7.static.flickr.com/6046/6350976644_176fedd7ef_b.jpg list] (all other packages are optional and are not used for this automation testing)
*** Enable USB Debugging on your device: Android Settings > Application settings > Development > USB Debugging
*** Perform a test to check if the device is connected correctly to your desktop machine:
**** Open the command prompt console
**** Go to {path}/android-sdk/platform-tools/
**** Type adb devices. A list with all the connected devices should be listed as you can see [http://farm7.static.flickr.com/6240/6350265993_c10cd5e6ef_b.jpg here]
*** Download java app : http://dump.lassey.us/time onto the desktop machine
*** Push time file to your device: adb push time /data/local
*** Change the permission of the file: adb shell chmod 777 /data/local/time
*** Download http://people.mozilla.com/~nhirata/Perf/startup5.html and http://people.mozilla.com/~nhirata/Perf/favorites2.html onto the desktop machine. Copy both files to your device's sdcard > download directory
*** To setup the local file on the network:
**** If you are on a mac, in the System Preferences, turn on the Sharing -> Web Sharing then the ip address of the website should be listed. Place the html files in the ~/Sites/ folder
**** If you are on windows:
*** Reboot the android device
*** run adb shell command in your terminal/command prompt window
*** for each of these '''[https://wiki.mozilla.org/QA_SoftVision_Team/Mobile/Performance_commands commands]''', run them and record the data at the spreadsheet based on the device, close the window and then force quit the application (note: do not go to the home screen after force quitting the application): <br> '''Note:''' be sure to throw out the first value of each set of run as it may be skewed due to loading of the cache.
** Results: you’ll see a number like “ELAPSED 800″ show up in the window and in the console as you can see [http://farm7.static.flickr.com/6047/6357597439_921f61c1d1_b.jpg here].
*** Samsung Galaxy S2 results: http://goo.gl/sHcGX
*** Motorola Droid Pro results: http://goo.gl/dML6s
 
* '''Gralloc testing''' <br>
** Since Fennec has moved from XUL to Native, another kind of testing is needed for better graphic performance. More details about Gralloc testing can be found [https://wiki.mozilla.org/QA_SoftVision_Team/Mobile/Gralloc_testing here]
 
=== Tasks related to bugs ===
==== Bug Verification ====
* here is the list with all the [https://bugzilla.mozilla.org/buglist.cgi?list_id=368824&resolution=FIXED&query_format=advanced&bug_status=RESOLVED&product=Fennec resolved fixed bugs]
* you can narrow down to a certain category or to latest fixed ones. (or depending on your device)
* Check the Steps to Reproduce.
** If the issues is solved please set the bug to VERIFIED FIXED.
** If the bug is reproducible please reopen it.
** If there are unclear steps, or the bug is ambiguous, please leave a comment asking for hints.
* In your comment please state your Environment (build id, device used and the OS version) and the steps you executed.
* When you do bug verification please update [https://spreadsheets.google.com/ccc?key=0AgbEknPON8vbdDJwUlotd3cyV3FlRFRnV3ZCSDl2MkE&authkey=CN37maMJ#gid=0 this document]
 
==== Bug Triage ====
* here is the list with all the [https://bugzilla.mozilla.org/buglist.cgi?list_id=2440022;query_format=advanced;bug_status=UNCONFIRMED;product=Fennec%20Native Native unconfirmed bugs]; [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced;list_id=2473148;bug_status=UNCONFIRMED;product=Fennec Fennec XUL unconfirmed bugs]
* [https://wiki.mozilla.org/index.php?title=Mobile/Triage first draft of triage lists]
* you can narrow down to a certain category or to latest fixed ones. (or depending on your device)
* Please try to reproduce the bug.
** If the bug is reproducible please set it to new and assigned the corresponding QA or dev person.
** If the bug is invalid (the behavior is as it should) please set it to RESOLVED INVALID.
** If the bug is not reproducible but the problem described is not an expected behavior please set it to RESOLVED WORKSFORME.
** If there are unclear steps, or the bug is ambiguous, please leave a comment asking for hints.
* When you do bug triage please update [https://spreadsheets.google.com/ccc?hl=ro&key=tFlMLxchXeNFfeXa41Lbv3Q&hl=ro#gid=0 this document]
 
==== Regression window wanted====
* here is the list with all the [http://bit.ly/regression-wanted Regression window wanted flagged bugs]
* you can find steps for making Regression window [http://quality.mozilla.org/docs/bugzilla/guide-to-triaging-bugs-for-firefox/finding-a-regression-window/ here]
 
=== Virtual Machines ===
====Perfecto Mobile====
* go to [https://www.perfectomobile.com/np-cas/login Perfecto Mobile site ]. For credential please ask [mailto:ioana.chiorean@softvision.ro Ioana Chiorean ]
* Quick [http://people.mozilla.org/~kbrosnan/androidVM.webm video overview of using the the VMs]
* Time is countered:
** signing in and browsing the device list does not use up time
* each VM you have open reduces the amount of time we have subtracted in increments of one minute. So please, close the VM if you are not actively using it
* we are on the restricted device list, only the Incredible will run Firefox Mobile
*[https://wiki.mozilla.org/index.php?title=QA_SoftVision_Team/Mobile/Review_Perfecto_Mobile Review of Perfecto Mobile]
 
====Devices Anywhere====
* Go to [www.deviceanywhere.com Devices Anywhere site]. For credential please ask [mailto:ioana.chiorean@softvision.ro Ioana Chiorean ]
** Select "Install DeviceAnywhere Studio"
** Once it has installed, run DeviceAnywhere Studio by double-clicking the Studio icon on your desktop
* This tool uses a Java client that you need to download after logging in on the website. Once you have installed the Device Anywhere client it will ask for a user name/password login. When you are logged in the client there will be a sidebar on the left listing the devices they have. Right click on one that you would like to run and choose acquire device. There will be a popup asking about signing up for the full version of Device Anywhere, choose no.
* The only real difference from usability is that to do a finger drag on a device you need to hold down ctrl and you will get an arrow indicating the direction of the drag. There are also some screenshot and button press logs that are available if you explore the tabs to the right of the running device.
*[https://wiki.mozilla.org/index.php?title=QA_SoftVision_Team/Mobile/Review_Devices_Anywhere Review of Devices Anywhere]
*[https://docs.google.com/spreadsheet/ccc?key=0AobT9pFawQ3DdDktLWUtMVlMQVprZ1pLdi1jbkpSRXc&hl=en_US#gid=0 Track of DA bugs]
 
=== Exploratory workarounds ===
* This task refers to use the application to make test that are not included in the Litmus test Suites.
* For each Domain explored, it is created a spreadsheet with the results met.
* please ask [mailto:ioana.chiorean@softvision.ro Ioana Chiorean]
 
===Tips===
====Sync====
*Changes to sync logging: https://philikon.wordpress.com/2011/06/16/aboutsync-log/ (Fixed {{bug|610832}}
====RTL====
*Nightly fennec RTL plugins can be found:http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-linux-l10n/linux-i686/xpi/
*Aurora fennec RTL plugins can be found: http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-aurora-linux-l10n/linux-i686/xpi/
*Beta fennec RTL plugin for beta 3 build 2 candidate can be found: http://ftp.mozilla.org/pub/mozilla.org/mobile/releases/latest-beta/linux/ar/ or http://ftp.mozilla.org/pub/mozilla.org/mobile/candidates/6.0b3-candidates/build2/linux/ar/install/
 
====News====
*You may find it useful to track information that you have may have missed during the week that could be related to our work. http://benjamin.smedbergs.us/weekly-updates.fcgi/project/fennec
====Languages====
*[https://l10n-stage-sj.mozilla.org/shipping/dashboard?av=fennec7 dashboard ]
====Native Fennec ====
*[https://etherpad.mozilla.org/native-fennec-blog-post Graphics]
====Fennec's permissions====
*[http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/AndroidManifest.xml.in#15 Android OS Permissions for Fennec]
= Working with Android SDK =
Confirm
2,280
edits

Navigation menu