HTTP authentication in automated testing – problems

and solutions

Igor Cernopolc Endava igor.cernopolc@gmail.com

Usage

Intranet portals

Back office applications

Cross domain authentication (basic)

Main problems

Non – HTML dialog

Main problems

Non – HTML dialog

Different interface/implementations along the browsers

Main problems

Non – HTML dialog

Different interface/implementations along the browsers

Consequence?

Consequence

Lots of workarounds for handling authentication

dialogs during automated web testing

Browser

based

Solutions

Browser based

Passing the username/password in the HTTP request (http://user:pass@domain.com)

Browser

based

Browser

based

Solutions

Browser based

Passing the username/password in the HTTP request (http://user:pass@domain.com)

Firefox profiles

Browser

based

Browser

based

Browser

based

Solutions

Browser based

Passing the username/password in the HTTP request (http://user:pass@domain.com)

Firefox profiles

Setting the appropriate cookie

Browser

based

Solutions

External

Firefox AutoAuth addon

Browser

based

Browser

based

Solutions

External

Firefox AutoAuth addon

java.awt.Robot class

Browser

based

Browser

based

Browser

based

Solutions

External

Firefox AutoAuth addon

java.awt.Robot class

Autoit, Siculi scripts

My Solution

Webdriver

Java

My Solution

Webdriver

Java

+

AutoitX

My Solution

Webdriver

Java

+ =

AutoitX

My Solution

My Solution

My Solution

My Solution

My Solution

My Solution

My Solution

My Solution

Limitations

Windows based

Selenium Grid

Limitations

Windows based → Siculi?

Selenium Grid → .exe script based calls?

→ duplicate workspace?

Conclusions

Don’t be afraid of using multiple tools when it is required. Combine and innovate and

you will succeed.

Please don’t forget to fill in the evaluation form

Thank you

Diamond Sponsors

Platinum Sponsors Gold Sponsors

Training Partners Media Partners Other Partners