Test executed on mobile agents missing connectivity information in JSON

[abhagupta]

Hi,
The connectivity value in the webpagetest test result (JSON) is not present on a test exectued on mobile agent. Is this something that is encountered by any one?

Mobile Agent :

"data": {

            "location": "Example_Nexus4:Nexus4 - Chrome",
            "from": "Nexus 4 - <b>Nexus4 - Chrome</b>",
            "completed": "Wed, 21 Oct 2015 00:01:05 +0000",
            "tester": "007886d5600d492f-172.29.236.53",
            "runs": 1,

Desktop Agent:

           "location": "WebPage2:Firefox",
            "from": "WebPage2 - <b>Firefox</b> - <b>3G</b>",
            "connectivity": "3G",
            "bwDown": 1600,
            "bwUp": 768,
            "latency": 300,
            "plr": 0,
            "completed": "Mon, 19 Oct 2015 23:04:13 +0000",

Notice the presence of connectivity object in Desktop version. Am I missing anything? My mobile tests run fine but I need the connectivity value to report the tests using sitespeed.io.

[bigethan]

this probably needs to be moved to the main webpagetest repo: https://github.com/WPO-Foundation/webpagetest the api just passes through the response. (Currently using --mobile sets the connectivity to 'Cable' for me regardless of setting - I'm using the latest AMI on EC2)

[jasonm]

Hi @abhagupta @bigethan - do you know if there's an issue on the main https://github.com/WPO-Foundation/webpagetest project that tracks this? Thanks!

[bigethan]

Update from me (though this isn't the right place): The 'cable' issue I ran into had to do with location being tied to connectivity. I was doing something like: webpagetest --mobile --conectivity 3GFast test http://www.google.com but that gives the default location, and location determines connectivity. Changing to something like --mobile --location us-east-1:Chrome --connectivity 3GFast fixed my issue.

[jasonm]

cc @adriangoe