wiki based automation testing: fitness & devops
TRANSCRIPT
Wiki Based Automation Testing : Fitnesse &DevOpsApril 23, 2016Subrato Ranjan Das
2Agenda:Quick takewaysDescription of the Tool - 2Advantages of Fitnesse - 2 Integration
of Fitnesse with Selenium (Browser testing), J-Shell (Unix testing) and JDBC (DB testing) -15
Exceptions handing scenario’s in Automation testing -10
How to use Fitnesse for DevOps -5Practical Example - 5Best Practices for Automation testing - 2Tool selections ideas - 10Q&A - 10
3
Quick Takeaways:
Awareness of wiki based automation testing frameworksAutomation tool selection processHow to increase turn-around time to report bugs, defectsAlternatives to expensive automation test tools that
perform better under certain situationsAdvantages & challenges of some popular automation
tools
4
Description of the tool Fitnesse is wiki based web server where testers can
write test cases in portal.
• Input file names • Business date ( for testing) • Forex rates• Instrument price• Counterparty business rating
• Initial Margin requirement• Processed File names• Variation margin• Risk status
Input Parameters
Output Parameters
5
Advantages of Fitnesse
Version maintenance for test casesRecords time to execute thus measuring performance from
previous resultsTest results history with compare functionalitySoftware installation not requiredCan be auto triggered when Developers are using Code
build in Hudson or Jenkins. Code will be tested as soon as they are checked in
Freeware
6
Integration: Fitnesse with Selenium, J-Shell and JDBCJava functions to achieve various kinds for testing like on
Unix, Database, BrowsersSelenium JAR files can be imported into the Automation
test project to run selenium FunctionsJ-Shell- for UnixJDBC for Database connectionsJars Document comparingJARs are java function libraries which contain in built
methods like openBrowser(), executeQuery() to be used in testing various applications manually tested in SQL , Browser and Unix box
7Exceptions handing scenarios 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
8
How to use Fitnesse for DevOps:Automation test cases can be written in advance before
code is preparedalthough this would clear technical details like expected
response message XMLUI needs to be prepared before business logic is written
over it
9
Practical Example:
Used for a banking applicationAn end to end testing was performed for collateral manage
ment applicationFiles for Forex rates, Balances & Positions for instruments
, Clearing house feeds for customers Buy/Sell portfoliosAll these files tested in Unix environment since Fitnesse
used J Shell to trigger Unix commands and fetch resultsJDBC was used to test database table updatesSelenium was used for performing transactions from GUI
10
Best Practices:
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 scenarios
Completed test pack to execute all test scenarios
11
Tool selections ideas:
Understanding client expectationsWhat testing tools to use for the applicationWhich tool to useWhich framework to use
12
Q&A
13
Thank You !