Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mobile Agent Tests missing connectivity value in response #598

Closed
adriangoe opened this issue Apr 7, 2016 · 2 comments
Closed

Mobile Agent Tests missing connectivity value in response #598

adriangoe opened this issue Apr 7, 2016 · 2 comments
Labels

Comments

@adriangoe
Copy link

The webpagetest result JSON seems to have no connectivity value when tests are executed on mobile agents such as Dulles_MotoG:Motorola G - Chrome

This causes problems in the API marcelduran/webpagetest-api/issues/54 and further down when I collect results in sitespeed.io sitespeedio/grunt-sitespeedio/issues/12

Quoting @abhagupta here, but I am experiencing the same problem:

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.

@adriangoe
Copy link
Author

cc @jasonm

@github-actions
Copy link

We're in the process of cleaning up issues on this project in order to ensure we're able to stay on top of high priority bugs and feature requests. As a part of this process, we're automatically closing any issues that have had no activity within the last two years, including this one, since the codebase has changed dramatically in that time. If you feel this is still relevant, please file a new issue using the relevant issue template so we can get it prioritized. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants