July releases round-up

By mark.

rWebUnit 1.3.1

The stylesheets, javascripts and image references in dumped html source are now substituted with absolute URL for better viewing.

TestWise 1.5.x

TestWise 1.5 introduced many new features particularly in refactorings and windows CHM help, checkout ChangeLog for details.

PRoR 186-v20

Gem upgrades: rWebUnit 1.3.1, win32 utils, fastercsv 1.5, prawn 0.5, ...


And many updates to the documentations.

CITCON 2009 Brisbane

By mark.

I attended the CITCON 2009 Brisbane (Continuous Integration and Testing Conference) over the weekend. It is a quite good one, the format Open Space is particularly interesting.

For my impression, this is a programmer/geek oriented conference, many Apple MacBooks, a lot of twittering. A lot of mentioning of 'Java', 'Groovy', and 'Ruby'.


Why Java (or C#) is not suitable as a functional testing language?

By mark.

One key difference between automated functional test scripts and application code is their target audience. The application code is developed and maintained by programmers, while the test scripts may be developed, executed and maintained by testers, developers, business analysts and even customers (_this backed by the fact TestWise is the most used software product for projects I know using it_).

The fact is that testers, business analysts and customers generally do not possess strong programming skills, and this changes the whole paradigm. It is not hard to imagine that a 85MB download of Eclipse (a Java IDE), configuration of library path and JDK path will do to a non tech-savy tester as the first chapter of automated testing orientation program. And you might hear screaming minutes later: "What does 'compiler error' mean?".

I believe automated tests shall use interpreted/scripting languages (such as Ruby) instead of compiled languages (such as Java), maybe that's why they are called "test scripts". And as a functional test script language, it should have following characteristics:

  • easy to learn,
  • no compilation required,
  • non proprietary,
  • concise, readable syntax,
  • extensible syntax to use domain specific language,
  • and ideally, one operation per line

Read full article

TestWise Community Edition

By mark.

The Community Edition is a complete product freely for personal use, and commercial use for up to 5 copies of software in one company or organization.

It does not have features used in project teams such as running tests against different environments, custom test suite, version control and reporting.

Productivity Guide - Snippets

By mark.

Snippets in TestWise IDE are little bits of text (abbrev.) that expand full test script statements. For example,

pssi     page_source.should_include(“TEXT“)

Press Ctrl + J, you will see a full list of snippets available, and it narrows down as you type.

Test Suites

By mark.

The term “Test Suite” in TestWise means a selected group of test files, this function (introduced since v1.2.2) gives you more controls over running tests, that is

  • individual test cases
  • all test cases in a test file
  • all test case in selected test files
  • all test cases in test files under selected folder To create a new test suite or edit existing one, select “Edit Configuration” in the drop down list on toolbar.

A window like this will show up to allow adding, removing or editing test suite. To run a test suite, click the drop down list (in the toolbar) to select it, then click

.

You might notice the “Run at line” button is disabled once a test suite is chosen, as it it not applicable. Select ‘Current File’ will enable it again.

March releases round-up

By mark.

A busy March sees the following releases.

TestWise 1.2.3

TestWise 1.2.x introduced some very useful features, such as

  • Test Suite
  • Run selected test scripts
I will cover them in detail in coming blog posts.

And the new installer now support uninstalling previous version if any.

PRoR 186-v17

Major changes: upgrade to latest Rails 2.3.2.

rWebUnit 1.2.1

rWebUnit 1.2 sees major documentation updates and new unit tests, and several API enhancements, eg.

try(15) { click_button("Pay") } # wait 'Pay' button for upto 15 seconds

And the API (RDoc) is now available online

Using TestWise for existing Watir scripts

By mark.

TestWise IDE v1.2 adds better support for running Watir scripts directly.

The demo project (project file c:\TestWise\samples\demo\demo.tpr) now includes one test case (TestWise_ajax_xxx) implemented in four different falvours:

  • rWebUnit
  • rWebUnit in RSpec
  • Watir script
  • Watir in RSpec
, which all can be executed in TestWise IDE.
 

Read full article