TestWisely RSS Feed

Watir-WebDriver support in TestWise2

Tue, 27 Jul 2010 00:00:00 GMT

Watir-WebDriver support in TestWise2

Selenium and Watir, as we know, are the two most popular open-source testing frameworks. The next big thing is WebDriver, which is now merged with Selenium 2. Thanks Jari Bakken (who is also the creator of Celerity), we have Ruby bindings for Selenium 2 and even Watir wrapper of it: watir-webdriver, which some might refer it as Watir 2.0. With watir-webdriver, users can pretty much reuse existing Watir scripts, with minor changes.

What are the benefits of using watir-webdriver comparing existing Watir 1.6.5?

Run same test scripts in IE, Firefox, Google Chrome and HTMLUnit (headless)
No JSSH plugin required for running tests in Firefox
Synergy of combination of Selenium and Watir

In last appearance at Watir Podcast, I said future TestWise versions will support WebDriver. Now you can try web-driver in IDE!

Download TestWise-2.0a1-setup.exe and install
In TestWise, open sample project c:\program files\testwise\samples\demo\demo.tpr (if you are using TestWise first, it shall be pre-loaded)
Select the first test script file (left mouse click the file name on the left): ajax_rwebspec_spec.rb,
choose your browser (IE, Firefox or Chrome), then run it.

Our initial impression with Watir-WebDriver is good and very promising, with a few issues:

Can't reuse existing browser window, has to start up a new one
Test execution is slower than Watir 1.6
Opening browser operation seems quite CPU intensive

Please note that both Selenium 2 and TestWise2 are at early development stage, so please use Watir 1.6.5 and TestWise 1.9 for production use.

Test sites with native Windows authentication

Wed, 14 Jul 2010 00:00:00 GMT

Test sites with native Windows authentication

Posted by Zhimin Zhan on July 14, 2010| Comments

For some sites (especially in .NET world), users are presented a native windows' authentication window (like below) before can access to it.

The standard open_browser in Watir won't work (get stuck), as it will be waiting response from the browser.

  open_browser("http://secure.site.com") # will stuck

To add a bit more complexity, we expect the same tests to pass whether user has already logged in or not.

The solution is:

Detecting Login Window using Ruby's timeout
Use AutoIt to fill user name and password in native Windows Login Window.

    begin
      Timeout::timeout(5) {
        open_browser("http://secure.site.com")
      }
    rescue Timeout::Error => e
      # debug "Timeout error on get to site, maybe asking for login"
      autoit = WIN32OLE.new('AutoItX3.Control')
      win_title = "Connect to edam.bluefirems.com.au"
      ret = autoit.WinWait(win_title, '', 10)
      if ret
        autoit.ControlSetText(win_title, "", "Edit2", username)
        autoit.ControlSetText(win_title, "", "Edit3", password)
        autoit.ControlClick(win_title, "", "Button3")
      end
   end

The above test scripts will work, but not readable. By applying 'Extract Function' and "Move to Helper" Refactorings in TestWise, we get:

    # ...
    rescue Timeout::Error => e
      # debug "Timeout error on get to site, maybe asking for login"
      # calling helper function in test_helper.rb
       
      login_as("zhimin@secure.site.com", "Secret")    
    end

blog comments powered by Disqus

Database Reset in Automated Testing

Fri, 11 Jun 2010 05:20:11 GMT

Database Reset in Automated Testing

Posted by Zhimin Zhan on June 11, 2010| Comments

At TIST conference, after my demonstration, on tester asked me "We saw you running the same test (changing password) twice, before and after refactoring, how could it work second time? The data has been changed from first run.". The answer was database reset, ie. the database is reset to the known state before running each test. As I have been doing this for a number of years now, it almost become second nature to me in terms of automated testing. To make the concept of database reset easy to remember, I call it "The Simpsons Pattern".

Benefits of database reset is so important that you probably will appreciate only after experience it. Once I asked a business analyst to rate his view of importance on database reset in scale of 1 - 10. He answered "9.... No, 10".

Develop tests without worrying of data changes caused by tests, what a feeling!
Faster test execution. Use seeded data records instead of creating data from scratch every time.
Always know data record states, great even for manual inspections of applications.

My typical RWebSpec test scripts like this:

suite "Group of related test cases" do
  include TestHelper

  before(:all) do
    open_browser
  end

  before(:each) do
    reset_database
    login_as("zhimin")
  end

  after(:each) do
    failsafe{ logout }
  end

  test "One test" do
    # might change application records
  end

  test "Another test case" do
    # doesn't matter the above test is run or not, as we start fresh
  end
end

Now comes the hard question, how could you implement database reset as testers? No, it has to been done by developers. If your team is doing Agile (or claiming so), go ask them, and it will be of great help for them as well. From experience, the better architecture, easier to implement database reset and the earlier the better.

blog comments powered by Disqus

Watir Podcast on TestWise

Fri, 28 May 2010 03:20:28 GMT

Watir Podcast on TestWise

My Podcast interview with Željko Filipin (the host of Watir Podcast) and Alister Scott (WebMaster of Watir.com) is now published: Watir Podcast #34 Zhimin Zhan on TestWise.

Ant today is 2nd birthday for Watir Podcast, so Happy Birthday! Thanks Željko and other contributors!

StoryWise is released

Fri, 14 May 2010 03:40:48 GMT

StoryWise is released

StoryWise, one of Agileway's Agile Testing Suite product, is a flexible web-based project management tool.

StoryWise is free and open source, released under the terms of the GNU General Public License v2 (GPL).

Requirement Management
Defect Tracking
Project Wiki
Time Tracking
Gantt chart and calendar
Requirement Traceability

Apart from being free, simple and easy to use, StoryWise distinguishs itself from others with one unique feature: Requirement Traceability, a term nowdays gradually fades out due to high hype with low benefits but lots of maintainence work.

StoryWise is different, it allows Requirement Traceability to be achieved simply and effortlessly. StoryWise was first demonstrated at 3rd Tianjin International Conference on Software Testing with very positive feedbacks.

Check it out!

3rd TIST Conference Slides and Videos

Mon, 26 Apr 2010 18:44:54 GMT

3rd TIST Conference Slides and Videos

Here are the slides and videos I presented at 3rd Tianjin Software Testing conference

StoryWise + TestWise = Effortless Requirements Traceability in Automated Testing (pdf)

Video Demonstrations － Quicktime

3rd Tianjin Software Testing Conference

Tue, 13 Apr 2010 15:53:19 GMT

3rd Tianjin Software Testing Conference

I will be delivering two presentations:

Maintainable Automated Functional Testing
StoryWise + TestWise = Effortless Requirements Traceability

at upcoming 3rd Tianjin 2010 International Conference on Software Testing in Tianjin, China.

If you are happen to be around Beijing at that time, you can catch up with me there.

TestWise Celebrity License

Mon, 29 Mar 2010 14:09:18 GMT

TestWise Celebrity License

As our appreciation for their hard work, talent and unselfishness, we offer ‘Celebrity License’ to

Creators/Developers of popular open-source projects, and
IT book authors

for free. If you are and interested in TestWise IDE, drop us an email.

To show your celebrity status, a medal is displayed next to your name (in About Dialog).

AgileWay's Agile Testing Suite

Fri, 19 Mar 2010 15:41:38 GMT

AgileWay’s Agile Testing Suite

TestWise 1.8.7 introduced a new feature: opening test cases in TestWise from Browser.

Double click C:\Program Files\TestWise\scripts\testwise_protocol.reg,

and intall the registry entry.

Enter a path to a test script file with ‘testwise://’ prefix in browser:

Click ‘OK’ button,

The test script file is opened in TestWise!

You might ask, what is the use for that? Yes, It does not provide benefits for functional testing alone. However, it opens the door for collaboration among tools on functional test cases.

You have seen TestWise and LoadWise (Runtime), the upcoming sister products are “StoryWise” : Requirement/Defect management tool and “BuildWise” : Continuous Build server, both with functional tests support.

TestWisely RSS Feed

Watir-WebDriver support in TestWise2

Watir-WebDriver support in TestWise2

Test sites with native Windows authentication

Test sites with native Windows authentication

Database Reset in Automated Testing

Database Reset in Automated Testing

Watir Podcast on TestWise

Watir Podcast on TestWise

StoryWise is released

StoryWise is released

3rd TIST Conference Slides and Videos

3rd TIST Conference Slides and Videos

3rd Tianjin Software Testing Conference

3rd Tianjin Software Testing Conference

TestWise Celebrity License

TestWise Celebrity License

AgileWay's Agile Testing Suite

AgileWay’s Agile Testing Suite

ANZTB 2010 Conference Slides and Videos

ANZTB 2010 Conference Slides and Videos