1 / 14

FitNesse + WATIJ = WitNesse (Or is it FATIJ)

FitNesse + WATIJ = WitNesse (Or is it FATIJ). Paul Lamb Vik Anantha. Summary. Browser simulation vs Browser automation (why we chose WATIJ) Testing by programmers vs Testing by business analysts (why we chose FitNesse) The happy co-incidence (putting them both together).

temima
Télécharger la présentation

FitNesse + WATIJ = WitNesse (Or is it FATIJ)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FitNesse + WATIJ = WitNesse(Or is it FATIJ) Paul Lamb Vik Anantha

  2. Summary • Browser simulation vs Browser automation • (why we chose WATIJ) • Testing by programmers vs Testing by business analysts • (why we chose FitNesse) • The happy co-incidence • (putting them both together)

  3. Browser simulation vs Browser automation

  4. HttpUnit • com.meterware.httpunit.WebConversation simulates a browser. • maintains session context via cookies returned by the server. WebConversation wc = new WebConversation(); WebResponse resp = wc.getResponse("http://google.com" ); WebForm form = resp.getFormWithName("f"); form.setParameter("q", "httpunit"); resp = form.submit();

  5. HttpUnit • Package com.meterware.httpunit.parsing contains classes to control HTML parsing. • Does it emulate the same type of parsing that IE Supports? • com.meterware.httpunit.scripting contains classes to evaluate javascript. • Does it evaluate javascript the way IE does? • “JavaScript support is very basic at present. The near-term goal is full JavaScript 1.1 support.”

  6. WATIJ(Web Application Testing in Java) • watij.ie automates a browser • Creates new instance of IE or attaches to an instance IE ie = new IE(); ie.start("http://google.com"); ie.textField(name,"q").set("Watij"); ie.button("Google Search").click();

  7. Other Browser Automation tools • WATIR (wtr.rubyforge.org) • Ruby based • SAMIE (samie.sourceforge.net) • Perl based • PAMIE (pamie.sourceforge.net) • Python • Selenium (www.openqa.org/selenium) • Is it really Browser automation?

  8. Testing by programmers vs Testing by business analysts

  9. FitNesse (Tests) • Tests are expressed as wiki tables of input data and expected output data • Written by non programmers

  10. FitNesse (Fixtures) • Enables System Under Test to be testable by wiki table based tests. • Written by programmers public class Division extends ColumnFixture { public double numerator, denominator; public double quotient() { return numerator/denominator; } }

  11. Sweet Spot • Lets non programmers write automated tests. • Allows tests to be written directly against the relevant business logic code. • Provides a modular structure for organizing test cases. • Fixtures provide a way of defining a testable “unit”.

  12. The happy co-incidence

  13. WitNesse • Is a WATIJ Fixture for FitNesse • Allows WATIJ tests to be written with wiki tables.

More Related