Wiki Based Automation Testing using Fitnesse - with relevance to DevOps

Description of the Tool

How to integrate Fitnesse with Selenium (Browser testing), J-Shell (Unix testing) and JDBC (DB testing)          

Advantages of using Fitnesse 

Exceptions handing scenario’s in Automation testing

How to use Fitnesse for DevOps

An Example where this was used for Banking application and how it benefitted the Client.

Best Practices for Automation testing

Tool selections ideas

 

 
1 favorite thumb_down thumb_up 6 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Description of the Tool

Fitnesse is wiki based web server where testers can write their test cases in the web portal. These test cases will be self-explanatory. The Input parameters for a test case can be put in Variables for example we would need:

  • Input file names 
  • Business date ( for testing) 
  • Forex rate for a particular currency

The Output parameters can be calculated using Fixtures (code written in Java).

  • Initial Margin requirement
  • Processed File names

How to integrate Fitnesse with Selenium (Browser testing), J-Shell (Unix testing) and JDBC (DB testing)          

  • Java functions to achieve various kinds for testing like on Unix, Database, Browsers
  • Selenium JAR files can be imported into the Automation test project to run selenium Functions
  • J-Shell- for Unix
  • JDBC for Database connections
  • Jars Document comparing
  • JARs are java function libraries which contain in built methods like openBrowser(), executeQuery()  which can be used in testing various application which need to manually test in SQL , Browser  and Unix box

Advantages of using Fitnesse 

  • Version maintenance for test cases
  • Records time to execute hence also tells us if performance has improved/degraded from previous run results
  • Test results history with compare functionality
  • Need not require testers to install any software in their machines to run Fitnesse since this tool would be kept in a Automation test server and testers can update, run test cases on the server
  • Freeware hence saving Budget
  • Can be auto triggered when Developers are using Code build in Hudson or Jenkins. Code will be tested as soon as they are check in.

Exceptions handing scenario’s in Automation testing

  • Exceptions handling mechanism in Java can be used effectively for handling exceptions like Connection timeout in SQL, Web page reload required or Unix server is slow to response

How to use Fitnesse for DevOps

  • Automation test cases can be written in advance before code is prepared although this would clear technical details like expected response message XML or UI needs to be prepared before business logic is written over it.

An Example where this was used for Banking application and how it benefitted the Client.

  • An end to end testing was performed for Collateral management application
  • Files  for Forex rates, Balances & Positions for instruments, Clearing house feeds for customers Buy/Sell portfolio 
  • All these files was tested in UNIX environment since fitnesse used J Shell to trigger unix commands and fetch results
  • JDBC was used to test database table updates
  • Selenium was used for performing transactions from GUI

Best Practices for Automation testing

  • Automation testing pack should be run for regression test scenarios only 
  • Automation should run as a Pack of test cases to test a Module or System End to End completely since individual test case execution in Automation wastes time and effort
  • Regularly check with client after every new update regarding critical business logic testing
  • Automation test pack to be divided between High risk test pack for critical scenario
  • Completed test pack to execute all test scenarios

Tool selections ideas

  • Understanding client expectations
  • What testing tools to use for the application
  • How to decide which tool to use and which framework to use

Learning Outcome

  • Audience will be aware of wiki based automation testing frameworks. 
  • Automation tool selection process
  • How to increase turn-around time to report bugs, defects.
  • Alternatives to Costly automation test tools which can sometimes perform better on certain situations
  • Advantages & Challenges of some popular automation tools

Target Audience

Manual Testers, Automation Testers, Architects, SME’s, Project managers, Business Analysts, Developers

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • subrato das
    By subrato das  ~  1 year ago
    reply Reply

    This will be a practical session. I will share my screen and show Java, Fitnesse and some tool selection techniques and show how to do it practically.

  • anup
    By anup  ~  1 year ago
    reply Reply

    I like the overall proposal, as well as the tool capabilities, as this would be great solution for automation, Great work Subrato!

  • Schalk Cronjé
    By Schalk Cronjé  ~  1 year ago
    reply Reply

    I like your outline around a number of integrations of other tools.

    Can we see a small demo during the presentation? Or at least simplified code examples in slides.

     

    Also Fitnesse has been around for a long time. What about mentioning the current maintenance status and how it positions to some other very popular automation frameworks (not too much, just so that people can see you have done some reading/research). Remember that with these sessions we do not want to sell a framework as the best thing since sliced bread. We want people to obtain knowledge so that they can make an informed decision for themselves as to what tool would work best for their context.

     

     

    • subrato das
      By subrato das  ~  1 year ago
      reply Reply

      Thanks for your interest on my Proposal. Yes I am planning to show a demo on using Fitnesse tool. I have been in Automation testing for quite some time and currently working as an Architect. My favorite option is to use Java API where we are using multiple interfaces like unix, db & soap xml. Considering it has significantly higher advantages over QTP and other .net based tools. Since Java is architecture neutral you can use it in a variety of situations like on UNIX, SQL, Databases and Mobile testing as well.  Java also has Exception Handling mechanism  which helps us if there is some exception which might occur in the test environment during the execution like Database is down or table is locked or Unix systems are overloaded. Through EH you can easily clear such obstacles. Since Fitnesse is written in Java and fits easily in Eclipse IDE in Java. I have preferred it over other tools for preparing a Framework which will work for a Bank application with multiple interfaces.

      • Renu Rajani
        By Renu Rajani  ~  1 year ago
        reply Reply

        Interesting!

         

        From: Global Test Retreat [mailto:info@confengine.com]
        Sent: Thursday, March 03, 2016 12:22 PM
        To: Anish Cheriyan; Schalk Cronjé; Aditya Garg; Brijesh Deb; Amit Janorikar; Dinesh Madne; Rajani, Renu
        Subject: Speaker replied to a comment on Wiki Based Automation Testing using Fitnesse - with relevance to DevOps

         

        Dear Committee Members,

        Your proposal Wiki Based Automation Testing using Fitnesse - with relevance to DevOps has received a new comment from subrato-das

        Thanks for your interest on my Proposal. Yes I am planning to show a demo on using Fitnesse tool. I have been in Automation testing for quite some time and currently working as an Architect. My favorite option is to use Java API where we are using multiple interfaces like unix, db & soap xml. Considering it has significantly higher advantages over QTP and other .net based tools. Since Java is architecture neutral you can use it in a variety of situations like on UNIX, SQL, Databases and Mobile testing as well.  Java also has Exception Handling mechanism  which helps us if there is some exception which might occur in the test environment during the execution like Database is down or table is locked or Unix systems are overloaded. Through EH you can easily clear such obstacles. Since Fitnesse is written in Java and fits easily in Eclipse IDE in Java. I have preferred it over other tools for preparing a Framework which will work for a Bank application with multiple interfaces.


        Visit https://confengine.com/global-test-retreat/proposal/2212#comments to respond to the suggestion OR simply reply to this email (Please make sure, you delete the previous comment's content from the email before replying.)

        Regards,
        Global Test Retreat Team
        aditya.garg@agiletestingalliance.org
        https://confengine.com

        You are receiving this email from ConfEngine on behalf of Global Test Retreat. Thanks for using ConfEngine's Conference Submission System.

        This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

      • Schalk Cronjé
        By Schalk Cronjé  ~  1 year ago
        reply Reply

        Thank you Subrato for clarifying. PLease rememebr that your context could differ vastly from that of memebers of the audience, so it is useful to keep the examples practical enough so that people could hopefully abstract it away into their own situations. Obviously adding in story-telling from your own experience from Fitnesse will help.