Recent changes to Home

Discussion for Home page

Olivier Meurice — Thu, 09 Oct 2014 06:58:13 -0000

Release 1.2-SNAPSHOT

Picvert is now dependency version agnostic.
As a consequence upgrading Aigrette is as easy as renaming the latest aigrette-{release}.jar to aigrette.jar then copying the library to the Picvert lib folder.

Discussion for Home page

Olivier Meurice — Thu, 04 Sep 2014 11:16:02 -0000

Working with a database connection

Some commands for working with a database are included in the internal command set of Picvert:

DBOPN to open a new connection

DBSEL to run a query

DBCLS to close an opened connection

Picvert is written in Java and therefore needs a JDBC driver to work with any database.
The JDBC library for the target database must be copied in the /extlib directory and the driver class must be specified in the DPOPN command.

For instance here is a command for opening a connection to a PostgreSQL database:

DBOPN!::org.postgresql.Driver,jdbc:postgresql://localhost:5432/databasename,user,password,DBCON

This command open a connection to the database 'databasename' of the local PostgreSQL with user 'user' and password 'password'. The connection object is put in the variable DBCON and will be available for subsequent operations (queries) with that database.

Let's see how we could perform a query:

DBSEL::@DBCON@,select zipcode from address where city = 'Brussels',RES

The command DBSEL is used to execute a query that get the zip code from the adress table for the city 'Brussels'. The result is an instance of List<Object> put in the variable RES.

To get the zipcode of a city name that is given as parameter we could have written:

DBSEL::@DBCON@,select zipcode from address where city = @CITY@,RES

The variable CITY must obviously contain the name of the city we want to get the zipcode.

When we no longer need the database connection we can close it with the statement:

DBCLS::@DBCON@

Discussion for Home page

Olivier Meurice — Fri, 25 Jul 2014 13:00:36 -0000

Logging

Picvert is generating three outputs:
- A technical text log which is appended at each run.
- A text report with very few details that summarize the tests executions, also appended.
- An XML Junit-formatted log that may be parsed by CI tools like Jenkins.

Discussion for Home page

Olivier Meurice — Wed, 23 Jul 2014 06:56:59 -0000

Adding new command

Adding a new command is quite easy, just follow these steps:

Create a new class that implements IProcessor and extends
AbstractCommandProcessor from the picvert-api module.

Implement the method process(List<String> params, VariableStore store):
CommandResult where params is the parameters of the command and store contains all
the variables with their values that have been initialized during the script
execution. It is an IN/OUT parameter, that means that new data can be added
to the store in the method implementation.

Package the class in a new jar file

Copy the Jar file in the extlib folder of picvert

Add the package of the new command in the picvert.properties file
processor=com.mycompany.myfirstprj,com.mycompany.mysecondprj

Note that extlib folder and picvert.properties must be in the same directory
than the picvert jar file.

Discussion for Home page

Olivier Meurice — Wed, 23 Jul 2014 06:55:39 -0000

Writing an automated scenario

So far the syntax of Picvert script is quite simple and was designed to
facilitate its parsing with few Java code.
A script is composed of a sequence of actions to perform each followed by its
comma-delimited parameters. The command and the parameters are separated by a
double colon (::).
Example:
COMMAND::PARAM1,PARAM2,...PARAMn

Internal commands

A collection of command are included in the tool and are obviously available
for scripting.
Run java picvert -h to get a list of available commands.

Variables

Picvert support a simple variable mechanism. Indeed some commands may store a
result in a variable that may be used later as another command parameter.

Example:
PUT::HELLO,VAR
ECHO::@VAR@

Executing this script will output "HELLO" to the console.

Loop

Two different loop are supported by Picvert.

The simple loop for executing a block of commands multiple times:

LOOP::2
ECHO::Looping
ENDLOOP

The concurrent loop to execute a block of commands multiple times in separated
threads:

CONCURRENT::2
ECHO::A thread has been created
ENDCONCURRENT

Conditional execution with if

To perform an action depending on the result of another action use the
IF/ENDIF commands:

PUT::1,VAR
if::@VAR@,==,1
ECHO::VAR = 1
ENDIF

The IF command takes three parameters: a first value or variable, an operator and a
second value or variable. Invoke the help to get all the available
parameters.

Discussion for Home page

Olivier Meurice — Wed, 23 Jul 2014 06:52:02 -0000

Running Picvert

Prerequisites

Install the JRE >= 1.7

Executing Picvert from the command line

Picvert is a Java program that is executed from the command line.
Here below the list of available parameters:

-l logfile
Specify the log file containing detailed information

-r reportfile
Specify the reporting file with valued information about test execution

-h
Print help about the available command

Example:

java -jar picvert-{version}.jar -l logger.log -r report.txt scenario.run
With scenario.run the picvert script file containing the commands to execute.

Discussion for Home page

Olivier Meurice — Tue, 22 Jul 2014 12:55:46 -0000

Installation

Install the binary package

Unzip the picvert-{version}.zip archive in the desired location.

Build from the sources

Prerequisites

Maven release > 3.0.5 must be installed and mvn command must be in the PATH.

Build Picvert

Get the sources from sourceforge.net
Open a shell and cd to the project root directory and run the command:
mvn clean compile package.
The archive picvert-{version}.zip is built in the picvert-core/target
directory.

Discussion for Home page

Olivier Meurice — Tue, 22 Jul 2014 12:34:04 -0000

Introduction

Picvert is an extensible automation tool written in Java initially developed to perform black box or
end-user tests. It may also be used to automate other processes involving
multiple systems.

To define a test scenario it is necessary to write a script using the simple
Picvert script syntax.

The extensibility is obtained by adding new commands. It is achieved by
creating new classes that implement a specific interface. The new classes
must be packaged in a jar file that will be used by picvert at runtime.
Indeed the new command classes extend the command set that may be used in the
Picvert script.

Home modified by Olivier Meurice

Olivier Meurice — Fri, 14 Mar 2014 07:34:44 -0000

Welcome to your wiki!

This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].

The wiki uses Markdown syntax.

Project Members:

Olivier Meurice (admin)