Testing automation #235
Comments
|
@rxaviers can you follow the usage instructions on here? https://github.com/browserstack/browserstack-runner It should be really easy to get running. Just make sure you've got Would be good to get some feedback from someone who hasn't used the tool before. Please let me know about any issues, no matter how tiny. |
|
I assume you have used it before then. Do you have any project with this setup? I've come up with the below browserstack.json: {
"username": "<username>",
"key": "<key>",
"test_framework": "qunit",
"test_path": ["test"],
"browsers": [
"chrome_previous",
"chrome_latest",
"firefox_previous",
"firefox_latest",
"ie_8",
"ie_9",
"ie_10",
"ie_11",
"ie_latest",
"opera_12_1",
"opera_previous",
"opera_latest",
"safari_5_1",
"safari_previous",
"safari_latest"
]
}Questions: "test_framework": "qunit",
"test_path": ["test"],Tests should be executed using "browsers": [...]Globalize supports http://jquery.com/browser-support/, except IE6 and IE7 right? What are the keywords for mobile? Is config missing any browser entry? |
|
|
Note I am not worried about grunt integration. My concern is whether or not executing |
Why?
Excellent! |
|
I lost track of our IRC conversation. What was your last result after changing the |
|
I just pulled and ran Running "qunit:unit" (qunit) task
Testing http://localhost:9001/unit.html
>> PhantomJS timed out, possibly due to a missing QUnit start() call.
Warning: 1/1 assertions failed (0ms) Use --force to continue.Seems pointless to run tests through browserstack when they don't even run through PhantomJS. Once that works, could you retry with browserstack-runner? I suggest to start with just one browser, that will speed things up a lot. |
|
It works just fine to me... I have double checked by cloning Globalize into a brand new directory, npm and bower installed dependencies, ran Could you double check yours please? PS: What command does browserstack-runner actually run? |
|
I've tracked down the problem within browserstack-runner and sent a PR: browserstack/browserstack-runner#83 Once that is merged and released it should work fine. I had a green run locally without timeouts. |
|
👍 |
|
@jzaefferer your PR is merged. Are we good to proceed? |
|
Sure. It was working for me with the patch, so can you give it another try? |
|
I've updated my browserstack-runner to 0.1.14. But, I'm getting this error There's no BrowserStackLocal file in my filesystem. Although, I do find the |
|
I have pushed my code in here (which is just the config file) https://github.com/jquery/globalize/compare/fix-235-testing-automation?expand=1 in case you need to see it. |
|
@rxaviers I ran into this same error working on this for mobile after we talked tonight. Got up to 6 files running and passing in mobile but when I added the file https://github.com/jquery/jquery-mobile/blob/master/tests/unit/page-sections/index.html i started getting this error |
|
Thanks @arschmitz for letting me know |
|
Oh well. Can either of you report that against the project itself? |
|
Include mobile browsers #278 |
|
For the record, that's the issue we had browserstack/browserstack-runner#91 . Now, browserstack-runner works and it submits the tests just fine. Although, the results are inconsistent, ie. tests fail intermittently when ran automatically. But, they pass when ran manually. |
|
#370 fixed several issues highlighted by running through browserstack-runner. Adding #367 (browserstack.json) still needs some work, should at least add functional tests to the mix. |
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes #235
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes #235
Uses a separate config file for IE8: BROWSERSTACK_JSON=browserstack-ie8.json browserstack-runner Ref #235
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes globalizejs#235
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes globalizejs#235
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes globalizejs#235
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes globalizejs#235
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes globalizejs#235
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes globalizejs#235
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes globalizejs#235
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes globalizejs#235
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes globalizejs#235
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes globalizejs#235
As for the obscured credentials: Those are easy enough to decode, the point is to avoid them being searchable, that is a search for the relevant keywords on GitHub won't immediately show these credentials. This is a temporary solution until Travis CI implements a proper one. Fixes globalizejs#235
|
WIP PR #450 |
|
Close in favor of #450 |
|
Actually, reopen. Should be fixed by #450. |
We want to test this in all supported browsers automatically. I'll look into creating a configuration file for
browserstack-runnerto see if that works here. Otherwise we can try it with TestSwarm.The text was updated successfully, but these errors were encountered: