#saucelabs

[simplythetest]

Some Thoughts on Software after SauceCon

It has been a hot minute since I've blogged - for several reasons including juggling child care, pandemic-related changes, and a busy time at work - and a week ago was SauceCon which I was fortunate enough to be a part of. It got me thinking about some things, so here they are in no particular order:

Virtual conferences are still just ok compared to real-life conferences, even if well-executed

Seriously, if you are a developer and you want to really level up your skill-set, join a sales team or customer-facing role.

High school english classes were probably the most helpful education I've had in terms of skills I use on a regular basis.

Low-code tools - for software testing or otherwise - are here and some of them are actually good, so get used to it.

A while back during a conversation with software developers, one developer commented that every good software tool choice depends on the context. Sometimes I needed to be reminded of that.

"Just use Selenium" is not a testing strategy. Not even close. You need more than a tool or piece of software.

Also for the love of all things Good, please treat parallelization (or p15y) a first class feature of your test automation

There's something good about Robot Framework, the community, that translates to Robot Framework, the tool somehow.

Totally my personal opinion and experience, but I'm not really a fan of tools with a vertical learning curve.

It is mind blowing what can be done with software these days with minimal effort, from a software engineering perspective.

If you're not paying attention to Kelsey Hightower, Maaret Pyhäjärvi, Nikolay Advolodkin, Titus Fortner or Angie Jones, you should really start doing that.

[khyati-sehgal]

Cross browser testing via Sauce labs?

Cross browser testing via Sauce labs?

Learning starts when you start experimenting. Be it in Information Technology or layman’s life.

I will be using this space to make you understand a tool which will be of great help, not only for all the Software QA but to the Product Owners, Developer, stakeholders, etc. It has all the solution to the issues we foresee in day-to-day life. As we know in Agile we always define the Acceptance…

View On WordPress

[szilvirj]

I was really impressed with how clearly this post explained / summarized testing and why it's worth moving away from waterfall and towards agile methodologies! #softwareqatesting101 #sfwqatest101 #saucelabs @saucelabs @facebook https://m.facebook.com/story.php?story_fbid=1880629265547562&id=1631270540483437 (at Sauce Labs)

[ely90h]

#sanfrancisco #saucelabs #cityhall #sunset (at InterContinental San Francisco)

[jasminenoack]

Dear Craigslist, seeking mortal foe. Have secret identity that nobody can know

Now hiring

Sometimes I work, sometimes I do my own thing. This weekend was one of those times that I mostly worked. I have been working on some large overarching projects which require a lot of work and are unfortunately the kind of projects that don't have a defined done point. So far it has gone super well. I have been able to get everything working that I wanted to get working some things are much more complicated than necesarry and some are much simplier. I'm generally a little obsessive and don't stop until I can get stuff to work. So this weekend we were mostly talking about SauceLabs.

One of the big things I needed to tackle was how to run robot on sauce labs. Unfortunately, it turned out the only tutorial that I could find for this I couldn't get to work. For whatever reason Selenium2Library seems to hate the version of robot or python or something. Whatever it was I finally gave up and decided to approach it like I was trying to pull two things together that no one else had pulled together. Techanically all robot is really doing is running python so it I could get it to work in python it only made sense that it should be equally workable in python run by robot.

The main problems with this over unittest.

I couldn't find a way to get a single run to generate all the tests for me.

I didn't set up naming well.

Perhaps great things:

It seems reasonably possible to generate all libraries this way.

There is a damn good library for running concurently. Unfortunately this library does break some stuff. It appears to get lost when it's looking for the files if we use a robot output directory. Perhaps I will look at solving this problem I haven't really thought about it at this point.

I also looked at ways to set the host file. Amazingly this appears to be super easy. It does look like it might be prudent to create a settings directory in QA for robot settings, executable settings, etc.

Tomorrow I will probably look into how to actually build a single instance that does all of these things. Perhaps wrapping the driver and changing create and close functions. We shall see tomorrow.

[dansreadlist]

[niwaringo]

protractorを使ったe2eでのcookieテスト

最近ちょこちょことcookieのライブラリを作っていて困ったのがcookieのテストです。

やりたい事は、

アプリではなくライブラリのcookieのテスト

saucelabsでマルチブラウザのテストを自動化したい

という2点でした。

cookieの仕様上オプション部分のテストが困難

cookieはname,valueという必須要素に加えて、domain,path,expires,secure等のオプション要素を持っています。

そして、このオプション要素はJavaScriptから設定できるのですが、取得する事ができません。

例えば、

document.cookie = 'name=value; domain=.google.com; path=/'

と設定する事は出来ても、

document.cookie // -> name=value

取得できるのはname,とvalueのみです。

このため、Karmaのようなテストランナーでは正しくオプションを設定できているのか?というテストをすることが出来ません。

Seleniumを使ったCookieのテスト

そのためオプションを含めたテストをする場合は、Seleniumを使うことにしました。

selenium-server-standaloneをローカルで立ち上げてWebDriverを使ってテストする事でcookieのオプションを含めた確認をする事ができます。

利用するjavascriptファイルを読み込むhtmlファイルを作成して、そこにWebDriverを使ってアクセスして確認します。

protractorというe2eテストフレームワーク

WebDriverを使ったテストする時にオススメしたいテストフレームワークは「protractor」です。 protractorはangular.js用に作られたテストフレームワークですが、angular.jsを使わない場合でも非常にオススメです。browser.ignoreSynchronization = true;とする必要がありますが :|

webdriver周りのサポートが手厚い

protractor一番のおすすめポイントはWebDriver周りのサポートが非常に手厚い事です。

WebDriverを使う時はstandalone serverをダウンロードして、それを立ち上げて……等など心が折れるフラグがここかしこに散りばめられています。

これが、protractorを使うと、

npm i -D protractor

でインストールして、

./node_modules/protractor/bin/webdriver-manager update

とするとstandalone serverをダウンロードしてきてくれます。

あとは、

./node_modules/protractor/bin/webdriver-manager start

でサーバーをスタートして

./node_modules/protractor/bin/protractor /path/to/configfile

でテストを実施できます。上記のWebDriver周りを全てprotractorのエコシステムを利用することが可能になります。

promiseをいい感じにしてくれる

WebDriverJS のAPIは基本的にはpromiseで構築されていて、control flowというのでいい感じにしてくれます。protractorはこの流れにそって非常にテストが書きやすくなっています。

そんため、

it('read', function() { browser.executeScript(function() { document.cookie = 'name=value'; }); var cookie = browser.executeScript(function() { return tongs.cookie('name'); }); // console.log(cookie) <= promiseが帰ってくる expect(cookie).toEqual('value'); });

のように書いても、promiseをいい感じに処理してテストしくれます。注意すべきは実体はpromiseなので、上記でいうとconsole.log(cookie)などとすると、return tongs.cookie('name')の戻り値ではなく、promiseが戻ってきます。

saucelabsサポート

設定ファイルにsaucelabsの情報を記載しておけば、saucelabsを使ったテストを実施してくれます。

sauceUser: ***, sauceKey: ***,

並行処理もいい感じにキュー管理してくれているっぽい? karmaは並行処理が多すぎて途中でエラーになっていたけれどprotractorではそのような事は起きませんでした。

IEとSafariはselenium経由でexpiresが取れない

今回、一番ハマったのがココ。IEとSafariのドライバーはexpiresが取れないようです。

Issue 3456 - selenium - Expiry date for Cookie not returned for InternetExplorerDriver - Browser automation framework - Google Project Hosting

ココに気づかずに、実機ではエラーが出ないのに……と悶々と調査・コードの書き変えをしていました。

結論としては、テスト内でchromeとfirefoxの分岐を入れて、chromeとfirefoxだけでoptionのテストをするようにしました。

var optionExec = function(callback) { browser.getCapabilities().then(function(s) { if (s.caps_.browserName.match(/chrome|firefox/)) { callback(); } }); }; optionExec(function() { // set cookie and get Date it('expires(date)', function() { var date = browser.executeScript(function() { var tom = new Date(); tom.setDate(tom.getDate() + 1); tongs.cookie('name', 'value', {expires: tom}); return Math.floor(+tom / 1000); }); browser.manage().getCookie('name').then(function(cookie) { expect(date).toEqual(Math.floor(cookie.expiry)); }); }); });

色々とありましたが、今はe2eでcookieのテストを自動化できているので満足です。

[nordicjs]

Give Sauce Labs a high five!

An event like this would not be possible without the help of amazing sponsors. We're super proud and thankful to have Sauce Labs on board as one of our supporters. 

  Sauce Labs is a tight-knit team working to transform how software testing and development gets done. Their platform makes Selenium testing, JavaScript Unit testing, manual testing, and mobile application testing hassle-free.