Mark59 Version 5.2 is now AvailableThis is a minor release and an updated user guide is now available, see the Downloads section for more details

Mark59 Logo

Mark59 Performance and Volume Testing Framework

background image courtesy wickipedia: Exorcism_of_the_Gerasene_demoniac

Overview

The Mark59 Performance and Volume Framework simplifies JMeter performance testing via automated test execution, reporting, SLA comparison and trend analysis. Java Selenium can also be incorporated to accelerate script development.

Mark59 is an open-source Java-based set of tools, with the aim of providing the capability of performance testing applications in a regular, repeatable manner, by having a focus on the automated detection of SLA breaches in a test, and highlighting trends and issues with the application under test over time. It is designed so that this is achievable without necessarily needing to have purely specialist performance test skills.We’ve avoided calling Mark59 a ‘framework’, as that word is often used in test automation to describe ‘clever’ software hiding or overlying core technologies, so people using them don't have a fair chance to feel motivated and to learn the proper skills they need in the industry. Rather, for example, our integration of two of two popular products in test automation, JMeter and Selenium, along with the work we have put into our examples and documentation, hopefully gives Performance Testers and Automation Testers an insight into scripting skills that can be easily learnt and benefit each other’s skill sets.Mark59 was designed to run on Windows or Linux-based operating systems, and is compatible with Macs.

Sample Screens:

Downloads

Select the appropriate zip version to download the executable jar files and samples. Linux and Windows compatible.As of Mark59 v3+ all projects are contained in a single zip file.If you are looking for the source code, see: https://github.com/mark-5-9/mark59

Current Release:mark59-5.2.zip (245 MB)Release Summary:Version 5.2Changes for this release:

  • DataHunter Rest - 'otherdata' field is now optional when adding an Item

  • Selenium to 4.5.0 (chrome v106+), spring-boot to 2.7.4

  • Bug Fix: Spurious characters when using % sign in Trends Advanced selectors

  • Bug Fix: Broken links in Trends when graph is empty

  • Updated documentation

Previous Release:mark59-5.1.zip (245 MB)Release Summary:Version 5.1Changes for this release:

  • Metrics UI - Same-named Groovy parameters preserved on a Command change

  • Metrics UI - Limit on characters shown for a command on Command List change

  • LOGRESULTSSUMMARY JMeter parameter added to metrics api (for consistency with other logging options)

  • Metrics - default bypass of Kerberos for Nix (prevents JSch session stalling for an unconfigured implementations). See User Guide for details

  • Metrics API was producing a 'no mark59.properties' warning if run in a JMeter test with no Mark59 Selenium implementations

  • New mark59 property mark59.print.startup.console.messages. 'true' will output some basic config messages to console

  • Metrics - Improved New Relic sample (now uses okhttp). SQL 5.0 to 5.1 conversions included in Release

  • spring-boot to 2.7.3

  • Bug: Metrics discontinues Nix commands immediately on connection failure (was attempting to run a command after the failure)

  • Bug: An Encryption class in Metrics was not thread-safe (caused occasional dropout of Nix/Win connections during tests

  • Bug: Trends Load - invalid use of DUAL in PG database when loading Loadrunner mdb Session files

View https://github.com/mark-5-9/mark59 for more detailsDocumentation for the release can be found in the "Documentation" section.

Documentation

Our Mark59 User Guide documentation can be found below:Mark59 User Guide for Version 5 PDF (4.8 MB)Mark59 User Guide for Version 5 HTMLGet a feeling of how it works in a few minutes by going through the 'Quick Start' chapters.

About

The Background to Mark59

Mark59 started from some ideas conceived around 2014 and has since developed to our latest release. It was developed by a team of working Performance and Volume testers at the Australian Insurance Company IAG in Melbourne. Our team, more out of necessity to maintain multiple and varied applications, over time changed practices from a traditional way of testing to something very similar to what is now called Dev Ops, and created a set of tools on the way that has become Mark59.A core team has worked on the project for most of its life, but many, many ideas came from the excellent Performance Testers that have been part of the team over the years. Not to mention (the sometimes rather blunt but valuable) feedback we have received from our client projects and others. We hope we haven't missed too many from the acknowledgements, but great ideas and suggestions have come to us from many, so we fear we have.

The People

The Core Team:

  • Philip Webb

  • Dhivya Raghavan

  • Greg Johnstone

Major Contributors:

  • Michael Cohen

  • John Gallagher

  • Sanman Basavegowda

  • David Nguyen

  • Edmond Lew

Grateful Acknowledgements:

  • Stephen Townshend

  • Srivalli Krishnardhula

  • Pankaj Harde

  • Mallamma Ganigi

  • Gaurav Shukla

  • Nikolai Chetverikov

Our Banner and the name 'Mark59'

The banner is part of a medieval illumination of the Gerasene demoniac exorcism, courtesy wickipedia: ExorcismoftheGerasenedemoniacThe biblical story of the 'Exorcism of the Gerasene demonic' appears in the New Testament in all of the synoptic gospels (Mathew, Mark and Luke), but the most well known account is from Mark's gospel. At a critical point in the story Jesus challenges the demon in a possessed man to name itself, and discovers he is not facing one demon but many when the famous reply comes "My name is Legion, for we are many" (Mark 5:9).We couldn't help relating our (admittedly trivial) struggles with turning a single Selenium script into many with this wonderful story, and so 'Mark59.com'.

Contact

You can contact us to give suggestions or feedback via the form below.
Note that we are a small working team, but we will do our best to respond.