Grinder 3.4. Test Automation Study. Study. Version: 1.0 Stand vom: :40:00 Status: Erstellt Author: Liljana Pendovska

(1)

Grinder 3.4

Test Automation Study

Study

 Version: 1.0

 Stand vom: 14.04.2015 17:40:00

 Status: Erstellt

 Author: Liljana Pendovska

 Document-ID: TA-Studie-Grinder

(2)

TA-Studie-Grinder SWQL - PT Studie - Grinder.docx

I / II

Table of Content

D

OCUMENT

I

NFORMATION

... II

General ... II

Document-History ... II

Document-Quality assurance ... II

Purpose and contents of this document ... II

1. G

ENERAL

... 1

1.1. About the Developer ... 1

1.2. Product Portfolio ... 1

1.3. Program Parts ... 1

1.4. Supported Interfaces... 3

1.5. Introduction ... 4

2. S

PECIFICATION

... 5

2.1. Test Case Design ... 5

2.2. Data-driven Tests ... 7

2.3. Verifications ... 8

2.4. Extendibility ... 9

3. E

XECUTION

... 10

3.1. Planning ... 10

3.2. Interfaces ... 12

3.3. Error Handling ... 12

3.4. Test Reporting ... 12

4. A

DMINISTRATION

... 15

4.1. Installation ... 15

4.2. Integration ... 15

5. C

ONCLUSION

... 17

A

NNEX

... 18

Table of Pictures ... 18

(3)

II / II

Document Information

General

Connections to other documents:

This analysis is a part of test automation study by Software Quality Lab.

Receivers: -

Document-History

Version Status Date Responsible person

Reason for changes/ Comments

Document-Quality assurance

Rolle Name Reachable

(Place+Tel.+e-mail)

Action Date Signature

Author Liljana Pendovska Created 2010-11-02 Reviewer Johannes Hochrainer Reviewed 2010-11-10 Reviewer Gregor Hammerschmidt Reviewed 2010-11-22 Releaser Johannes Hochrainer Released 2010-01-24

Purpose and contents of this document

This document contains an objective analysis of a performance testing tool and it should be available as a decision base for the people interested in the selection of a new tool.

(4)

1 / 18

1. General

1.1. About the Developer

Grinder was originally developed for the book Professional Java 2 Enterprise Edition with BEA WebLogic Server by Paco Gómez and Peter Zadrozny. In the end of 2000 Philip Aston took the ownership of the source code and reworked it to create Grinder 2. Shortly after he began to work on Grinder 3, many new features were implemented such as Jython as scripting engine enabling powerful, expressive test scripts to be executed. 1

1.2. Product Portfolio

Grinder is a Java load-testing framework that makes it easy to run a distributed tests using many load injector machines. It is an open source tool with BSD style license2 and is used for testing HTTP web servers, SOAP and REST web services, application servers (Corba, RMI, JMS, EJBs) and many different custom protocols as well as basically anything that uses Java API. The testing scripts in Grinder are built in the powerful scripting language Jython which makes scripting flexible and uses the HTTPClient library3.Tests are monitored and controlled via the graphical console that comes in four languages English, German, French and Spanish.

1.3. Program Parts

Grinder, as shown on Picture 1, is comprised of the following processes:

 The Console is responsible for coordinating the other processes and for collecting the statistics

 Agent processes is a single agent process that runs on a test-client machine and is responsible for managing the worker processes on that machine

 Worker processes is created by the Grinder agent processes and is responsible for performing the tests

When an Agent process is started it tries to connect to the console so that it can receive commands. The agent process reads the local grinder properties file and starts the number of worker processes, specified in the properties file. The workers are responsible for starting the threads and for running the scripts.

These processes are regulated by two parts. Those are the console and the agent.

1

Information taken from Grinder home page http://grinder.sourceforge.net/

2

BSD licenses are family of permissive free software licenses.

(5)

2 / 18

Picture 1: Grinder processes1

The console (see Picture 2) is the graphical user interface used as a controller, pushing out scenarios and test cases (scripts) to agents that are running on load-injection machines. It has four tabs, each with a specific function:

 Script tab is used for script editing, setting up which scripts to run and for selecting the properties files.

 “Processes” displays information on the connection status between the console and the agents. During execution of the scripts it also shows the run time status of the connected load generators along with virtual users (threads) information.

 The result tab presents the tabular view of the run time test results with several instrumentations.

 Graphs - shows the graphical results during run time of tests with the 25 most recent tests per second (TPS) values for a particular test.

Beside these tabs, the Grinder console has the sample controller where the tester determines how the console captures reports from the worker processes and the process controls for sending signals to Grinder processes that are listening.

(6)

3 / 18

Picture 2: The Console

The console is optional, because any command can be executed with the command prompt. The core component of Grinder is the Grinder agent, which is responsible for creating the worker processes that execute the test scripts. There can be several Agents running at the same time, on more than one system, executing the same or different test scripts. Without the agent no tests can be executed .

Another part of Grinder with major importance is the proxy-based capture tool shown on Picture 3. This tool is used for recording scripts.

Picture 3: TCPProxy Console

Grinder Analyzer1 is an extra open source component that helps Grinder to generate better graphs and tables. This is external tool that uses the log and out files generated by Grinder console to create html reports that include a summary presented in form of a table with sortable columns.

1.4. Supported Interfaces

The Grinder is used for performance tests of:

 Web services with protocols such as SOAP, XML-RPC

 systems that are using POP3, SMTP, FTP, and LDAP protocols as well as RPC

(7)

4 / 18

 MOM based systems using protocols such as IIOP, RMI/IIOP, RMI/JRMP, and JMS

 it can be also utilized for testing databases using JDBC connection.

1.5. Introduction

Grinder, considering that it is an open source tool, has a fairly good user guide. Thanks to Grinder user community there are some good guides for Grinder available. This makes the first steps with this tool much easier. Some of those links can be found on the web page of Grinder. Also there is one official Grinder forum where people share experience with this tool.

(8)

5 / 18

2. Specification

2.1. Test Case Design

Tests in Grinder can either be recorded or written from the scratch. Setting up even simple tests in Grinder requires a good knowledge in writing Jython code, that’s why as a beginner it is better to start with the TCP proxy recording tool. This tool uses the common web capture technique of recording a session as it passes through a proxy. The proxy is used to create a Grinder script that can then be executed from an agent. To record a script, the browser proxy has to be set to direct the traffic through the Grinder proxy in order to capture the http traffic, as shown on Picture 4. After stopping the record process the generated Jython script will be written into grinder.py file. This script can be easily modified and changed using the grinder editor.

Picture 4: TCPProxy connections1

The anatomy of recorded test scrip is shown Picture 5.

(9)

Seite 1 von 2

Thank you very much

for downloading a public preview of our well known and highly appreciated tool studies.

If you’re interested in reading the whole document just apply here and request the document you want to read from our comprehensive set of studies already available.

For further information on our tool studies visit our web site.

(10)

Seite 2 von 2

Bitte ausgefüllt per Email an/ Please fill out and send to

info@software-quality-lab.com

Bestellformular für Tool-Studien/Order form for tool studies

An/to

Software Quality Lab GmbH Gewerbepark Urfahr 6 4040 Linz AUSTRIA Name/full name: Adresse/address: Firma/company: Email/email: Funktion/role: Telefon/phone: /

[bitte füllen Sie die Daten vollständig und korrekt aus/please supply correct and complete data]

Bestellliste/Order list

[bitte kreuzen Sie die gewünschten Tools an/please select the tool studies]

Weitere Informationen auf unserer Website www.software-quality-lab.com. Die Toolnamen und eingetragenen Warenzeichen sind Eigentum der jeweiligen Toolhersteller/Tool names are property of tool vendors.

Die Studien sind grundsätzlich auf Anfrage frei erhältlich. Software Quality Lab behält sich jedoch vor, die Aufwände für gewisse Branchen und Privatpersonen in Rechnung zu stellen (z.B. Beratungsfirmen, Toolhersteller usw.) Studenten erhalten die Studie zum halben Preis/All studies are basically free, except for certain branches of industry or private persons, for whom we invoice at cost. Students get a discount of 50%.

ALM, RM

 IBM Rational Requirements

Composer 4.0.2

 Jama Contour 3.61NEU!

 Micro Focus Borland Caliber  Microsoft Team Foundation

Server 2013

 Polarion ALM 2014  HP ALM 11  VersioneOne 13.0  Visure Solutions IRQA 4

Test Management

 Imbus TestBench 1.6.1  Micro Focus SilkCentral 2008  Microsoft VSTS 2010  Mozilla Testopia 2.1  Orcanos QPack 5  Polarion ALM 20121NEU!

 Siemens SiTEMPPO 5.8  TestLink 1.9.12  Seapine TestTrack 2012

Static Code Analysis

 SonarQube 4.5

GUITest Automation

 Appium 1.2.2

 Bredex GUIdancer 4.2  HP UFT Professional 10  IBM Functional Tester 8.1.0.3  Microsoft VSTS 2010  QF-Test 3.5.1 NEU!  Ranorex 3.3  SAP eCATT  Selenium 2.0  SmartBear TestComplete 9.3  SmartBear SoapUI 5.1 EmbeddedSystems  LDRA 8.0  Razorcat Tessy 2.6 Load/Performance  Apache JMeter 2.8  Grinder 3.4  HP LoadRunner 9.5  Neotys Neoload 3.0.3  SmartBear LoadUI 2.8.0 Unit Tests  Google Test 1.5  JUnit 4.11  NUnit 2.5.7

(11)

Software Quality Lab GmbH | info@software-quality-lab.com | www.software-quality-lab.com

www.software-quality-lab.com

V. 2 011 -1 2 LINz / VIENNA / GrAz / LUsTENAU / MUNICh

Consulting

Implementation

Training

Automation

Evaluation

Software Quality Lab is your competent partner in software quality and testing and one of the leading independent consulting companies in Austria. We specialize our-selves in the improvement of efficiency, quality and security in the fields of soft-ware development and system processes.

Your Partner for software quality and testing

Tools in TEC

Our TEC includes more then 40 installed tools from reputable manufacturer (e.g. IBM, HP, Micro Focus, Microsoft, Polarion, Siemens) as well as interesting newcomer products and alternatives from the open source area (e.g. JMeter, Selenium).

Further details can be found at www.tool-evaluation.com.

requirements elicitation, Creating a list of criteria

Tool review, Pre-selection of tools, Practical getting to know

the tools in the TEC

Workshop with 3-5 suitable tools, Proof of Concept, Planning and implementing

the pilot project

Integration with other tools

Our services around the tool selection

E

Time-saving: Tool selection in a few

days. No time-consuming research and product requests, no installation and testing.

E

Preparation of information for different

target groups – from technicians to the managing board.

E

Support provided by specialists, ranging

from requirements through to a proof of concept or a pilot project.

E

Comprehensible decision criteria: Using

special techniques we evaluate the tools together with you, basing on your require-ments as a foundation for your investment decision.

E

Large selection and direct comparison

of products ranging from market leaders through newcomers to open source software and freeware.

Your Benefit

All tools in TEC are up to date, installed and configured, furnished with examples and ready for demonstration. Practical work and getting to know the tools in a hands-on manner is also possible.

What is TEC?

The Tool Evaluation Center (TEC) is a neutral environment for evaluating software tools related to software development, through which you will receive a detailed, vendor-independent overview of the suitability of different tools for your software projects.