TEST AUTOMATION FITNESSE IS AN EASY TO USE WIKI WEB SERVER

FITNESSE IS AN EASY TO USE WIKI WEB SERVER
The wiki syntax in FitNesse is minimalistic and helps you concentrate
on the content. It has a rich-text editor for those not really into the
wiki markup. The rich-text editor has extra features to support table
creation and modification, something you‘ll love when creating test
tables in FitNesse.
EASY TO SET UP: JUST DOWNLOAD IT AND START IT
FitNesse comes as an all-on-one package. Getting started
with FitNesse is as simple as starting the Java .jar-file. Wiki
pages are stored as files, so there is no hassle with databases.
You can run FitNesse on your machine or on a server.
COMBINING ALL STEPS ON ONE PLATFORM
SPECIFICATIONS CAN BE USED AS TEST INPUT
All the steps A to D can be combined on one test page within
FitNesse, making the execution and maintenance of test cases
very easy.
Since FitNesse is a wiki, it’s not in the way when you reason about
requirements for your (software) project. FitNesse allows you to
validate those requirements with the actual software implementation. If your project is written in Java, it’s a piece of cake. However
FitNesse plays well with every language and environment.
Using the ‘test suite’ option within FitNesse it is even possible to
execute a suite: a combination of several test cases. Using this
FitNesse functionality will enable the creation of an automated
regression test set,making the way you test your PowerCenter
application even more efficient.
THE MAJOR LANGUAGES ARE SUPPORTED
TEST AUTOMATION
WITH FITNESSE
THE FULLY INTEGRATED STANDALONE WIKI
AND ACCEPTANCE TESTING FRAMEWORK
Yes! Whether your project is written in Java, Python or C#, FitNesse
can be hooked in and you can automate the test process. See the
PlugIns page for impementations.
From our experience putting a little more effort in test automation,
is money well spent. It helps to develop PowerCenter applications
efficiently and in a sustainable pace, without having to add test
resources the application gets more and more complex over time.
Get started at fitnesse.solutions
Please visit Informatica Marketplace for more information on Test
Automation using FitNesse.
CONSAG | CONSULTING SERVICES
Rozengracht 56-2
NL - 1016 ND Amsterdam
Fon +31.8787.0 33 04
info@consag.nl
www.consag.nl
© 2014 consag
Get started at fitnesse.solutions
The maintaining or developing of Informatica PowerCenter / ETL
applications can be a tedious and labor intensive job for software
testers. Especially when most tests are executed manually.
A
We experienced a lot of time was lost in the analysis of defects;
was it a software defect or caused by a mistake in the manual
test execution?
Putting some effort in automating test case execution definitely
helped to improve the efficiency and quality within the software
development process.
B
HOW TO AUTOMATE TEST CASE EXECUTION
If you want to fully automate the execution of your test cases for
PowerCenter applications, you need to be able to automate the
following steps within a test case:
A
POPULATE SOURCE TABLES WITH TEST DATA
B
RUN POWERCENTER WORKFLOWS
C
COMPARE THE ACTUAL OUTPUT IN THE TARGET
DATABASE TABLES WITH THE EXPECTED OUTPUT
D
CLEANUP THE USED DATABASE TABLES SO YOU
CAN RUN THE SAME TEST MORE THAN ONCE
The Open Source wiki FitNesse (www.fitnesse.org) is a great tool to
automate PowerCenter test cases; it is easy to setup and maintain.
As in the usage of each new tool, there is a learning-curve you
need to overcome. In the next sections we will elaborated how to
setup FitNesse for PowerCenter, helping you bridge the learning
curve faster.
POPULATE SOURCE TABLES WITH TEST DATA
There are different ways to start automating the population of test data into a source database. One way
would be to use SQL scripts. The tool FitNesse could
provide a solution, which is more easy to maintain by
less technically skilled users. Updating the test data
would be as simple as updating a wiki page.
RUN POWERCENTER WORKFLOWS
Same as with populating the database tables, there are
different options to automate starting up a PowerCenter
workflow. When using FitNesse, you will need a specific
fixture to connect FitNesse to the PowerCenter application.
This fixture should be a reusable fixture, so it can be used
To be able to start using FitNesse to populate source database
tables with test data you need:
1. FitNesse installed locally on your desktop or on a server
2. A FitNesse test page to put your test data in
3. A ‘fixture’; specific programming code to connect
FitNesse and the source database
for all workflows needed. This will prevent you from having to
create and maintain a new fixture every time a new workflow
is created.
Below an example is depicted of a FitNesse test page which
calls such a reusable fixture. By simply editing the text on
the FitNesse test page, a different workflow can be initiated.
A. An example of a table on a FitNesse test
page which can be used to start a workflow.
B. An example of a table
on a FitNesse test page
after having started a
workflow successfully.
C
COMPARE THE ACTUAL OUTPUT IN THE TARGET
DATABASE TABLES WITH THE EXPECTED OUTPUT
Comparing the actual and expected content within the
database tables could be done by SQL scripts as well as
FitNesse. Such a FitNesse table on a test page is shown
below. Test pages are easy to maintain and can even be
read or reviewed by business stakeholders.
D
CLEANUP THE USED DATABASE TABLES SO YOU CAN
RUN THE SAME TEST MORE THAN ONCE
C. An example of a table on a FitNesse test page after having compared the expected output of
a sql query with the actual content of the database table. If the expected output is exactly the
same as the actual content, the text is highlighted in the color green.
For removing the test case data or truncating database
tables, FitNesse can be used too, and the cleanup can be
easily maintained like in the previous steps.
Get started at fitnesse.solutions
The maintaining or developing of Informatica PowerCenter / ETL
applications can be a tedious and labor intensive job for software
testers. Especially when most tests are executed manually.
A
We experienced a lot of time was lost in the analysis of defects;
was it a software defect or caused by a mistake in the manual
test execution?
Putting some effort in automating test case execution definitely
helped to improve the efficiency and quality within the software
development process.
B
HOW TO AUTOMATE TEST CASE EXECUTION
If you want to fully automate the execution of your test cases for
PowerCenter applications, you need to be able to automate the
following steps within a test case:
A
POPULATE SOURCE TABLES WITH TEST DATA
B
RUN POWERCENTER WORKFLOWS
C
COMPARE THE ACTUAL OUTPUT IN THE TARGET
DATABASE TABLES WITH THE EXPECTED OUTPUT
D
CLEANUP THE USED DATABASE TABLES SO YOU
CAN RUN THE SAME TEST MORE THAN ONCE
The Open Source wiki FitNesse (www.fitnesse.org) is a great tool to
automate PowerCenter test cases; it is easy to setup and maintain.
As in the usage of each new tool, there is a learning-curve you
need to overcome. In the next sections we will elaborated how to
setup FitNesse for PowerCenter, helping you bridge the learning
curve faster.
POPULATE SOURCE TABLES WITH TEST DATA
There are different ways to start automating the population of test data into a source database. One way
would be to use SQL scripts. The tool FitNesse could
provide a solution, which is more easy to maintain by
less technically skilled users. Updating the test data
would be as simple as updating a wiki page.
RUN POWERCENTER WORKFLOWS
Same as with populating the database tables, there are
different options to automate starting up a PowerCenter
workflow. When using FitNesse, you will need a specific
fixture to connect FitNesse to the PowerCenter application.
This fixture should be a reusable fixture, so it can be used
To be able to start using FitNesse to populate source database
tables with test data you need:
1. FitNesse installed locally on your desktop or on a server
2. A FitNesse test page to put your test data in
3. A ‘fixture’; specific programming code to connect
FitNesse and the source database
for all workflows needed. This will prevent you from having to
create and maintain a new fixture every time a new workflow
is created.
Below an example is depicted of a FitNesse test page which
calls such a reusable fixture. By simply editing the text on
the FitNesse test page, a different workflow can be initiated.
A. An example of a table on a FitNesse test
page which can be used to start a workflow.
B. An example of a table
on a FitNesse test page
after having started a
workflow successfully.
C
COMPARE THE ACTUAL OUTPUT IN THE TARGET
DATABASE TABLES WITH THE EXPECTED OUTPUT
Comparing the actual and expected content within the
database tables could be done by SQL scripts as well as
FitNesse. Such a FitNesse table on a test page is shown
below. Test pages are easy to maintain and can even be
read or reviewed by business stakeholders.
D
CLEANUP THE USED DATABASE TABLES SO YOU CAN
RUN THE SAME TEST MORE THAN ONCE
C. An example of a table on a FitNesse test page after having compared the expected output of
a sql query with the actual content of the database table. If the expected output is exactly the
same as the actual content, the text is highlighted in the color green.
For removing the test case data or truncating database
tables, FitNesse can be used too, and the cleanup can be
easily maintained like in the previous steps.
Get started at fitnesse.solutions