Tales from the dark side:
   browser controller testing
         for webapps in
     Windows environment
            Adria...
Blackbox testing
           aka data testing, behavioral testing
           + only tests functionality
           + does n...
Webapp testing before 2004-2005

 Mostly browser simulator
 (headless) pattern
 eg. in Java:
 httpunit
 htmlunit
 ...
 (in...
2005 – AJAX becomes de facto standard
- Only HTML parsing is not good enough
- Rhino ? No support for browser-specific obj...
Windows !
+ massive user base
+ IE still the dominant browser
+ large variety of tools
(commercial and open-source)
+ OS a...
Mainstream opensource & free tools
for browser control/automation

Samie (Perl)
Pamie (Python)
WatiR (Ruby)
WatiN (.Net)
A...
But can you script any type of webapp ?

Take Gmail, for instance – hard to blackbox
(for sure it is instrumented for whit...
Yes you can.

One of the solutions:
●
  WatiN
http://watin.sourceforge.net/
●
  scripted with IronPython
http://www.codepl...
One more thing ...

                          9
Wurbe #5      Pag. 9/10
The Epiphany – testing is useless :)

“Instead of wasting your time with
tests, you'd better write
bug-free code in the fi...
Upcoming SlideShare
Loading in …5
×

Browser controller testing for webapps (in Windows environment)

3,253 views

Published on

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • valuable material
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total views
3,253
On SlideShare
0
From Embeds
0
Number of Embeds
118
Actions
Shares
0
Downloads
74
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

Browser controller testing for webapps (in Windows environment)

  1. Tales from the dark side: browser controller testing for webapps in Windows environment Adrian Spinei netuality.ro 1 Wurbe #5 Pag. 1/10
  2. Blackbox testing aka data testing, behavioral testing + only tests functionality + does not need server instrumentation + easy to understand - sometimes performed by humans (and humans do not like it) - relatively hard to maintain - coverage of what ? 2 Wurbe #5 Pag. 2/10
  3. Webapp testing before 2004-2005 Mostly browser simulator (headless) pattern eg. in Java: httpunit htmlunit ... (inspired from junit/xunit circa 1999 – Kent Beck, Erich Gamma) 3 Wurbe #5 Pag. 3/10
  4. 2005 – AJAX becomes de facto standard - Only HTML parsing is not good enough - Rhino ? No support for browser-specific objects - It's not easy to “rewrite” the browser Solution ? Browser controller – run a full fledged browser instance and use automation techniques to control and check data 4 Wurbe #5 Pag. 4/10
  5. Windows ! + massive user base + IE still the dominant browser + large variety of tools (commercial and open-source) + OS automation APIs - mono-platform - makes you totally uncool - definitely will not improve your sex life 5 Wurbe #5 Pag. 5/10
  6. Mainstream opensource & free tools for browser control/automation Samie (Perl) Pamie (Python) WatiR (Ruby) WatiN (.Net) AutoIT (Basic) ... probably more (just Google it) 6 Wurbe #5 Pag. 6/10
  7. But can you script any type of webapp ? Take Gmail, for instance – hard to blackbox (for sure it is instrumented for white box testing, debug, some REST equivalents, but that's not the point) ● (relatively) unpredictable id values ● very often, no names for elements ● compose mail = a SPAN element, not a link ● email body is written inside a ... BODY tag 7 Wurbe #5 Pag. 7/10
  8. Yes you can. One of the solutions: ● WatiN http://watin.sourceforge.net/ ● scripted with IronPython http://www.codeplex.com/IronPython ● spiced with WinForms.SendKeys ... demo time ! 8 Wurbe #5 Pag. 8/10
  9. One more thing ... 9 Wurbe #5 Pag. 9/10
  10. The Epiphany – testing is useless :) “Instead of wasting your time with tests, you'd better write bug-free code in the first place !” Customer, circa 2004 (name withhold to protect the innocents) 10 Wurbe #5 Pag. 10/10

×