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

Overview

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 popular products in test automation, JMeter and Selenium (or Playwright), 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: Version 6.0 (March 2024)

Download: mark59-6.0.zip
(556.2 MB download via Google Drive link)
Release Summary:Playwright has been introduced as a UI scripting alternative to Selenium. Most changes for this release are consequences of this.Details of changes for this release: https://github.com/mark-5-9/mark59?tab=readme-ov-file#releases


Previous Release: Version 5.7

Download: mark59-5.7.zip
(251.4 MB download via Google Drive link)
Release Summary:Changes for this release:

  • Scripting - JMeterFuntions: new set of Transaction Rename and Transaction Delete methods

  • Trends - new Application copy (copy/delete for rename) function on Application Dashboard.

  • Trends - new Application Ids are restricted to containing alphanumerics, dots, dashes and underscores.

  • Trends - tidy up selectors on Trends Graphic UI.

  • Bug: Title link in Datahunter corrected to point to Overview page

  • Bug: Correct sample test plan DataHunterLifecyclePvtScriptUsingApiViaHttpRequestsTestPlan to use /api/policiesBreakdown

  • Bug: Metrics (MAC only) H2 sample database was missing entries to capture CPU Memory and CPU (used in the Quick Start Demo)

  • Minor tidy up of JavaDocs and Selenium sample scripts.

  • Dependencies: spring-boot to 3.2.0, selenium to 4.15.0 (to chrome v119), org.json to 20231013

Summary of changes with potential incompatibilities for this release:

  • H2 Database format has changed

This is due to an update in the underlying SpringBoot framework changing the version of H2 from 2.1 to 2.2. If you have existing H2 databases from running the Mark59 Quick Start Demo previously (which uses H2), you will see an error on start-up of affected Mark 59 Web Applications when using H2 similar to:org.h2.jdbc.JdbcSQLNonTransientConnectionException: Unsupported database file version or invalid file header in file "C:/Users/{userid}/hunter.mv.db"The solution is simply to delete all existing H2 database file stores. They are re-created when you run the demo next time.If for some reason you wish to restore the data in your H2 database(s), please refer to
https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-3.2.0-Release-Notes#h2-version-22


View https://github.com/mark-5-9/mark59 for additional details and older releases.

Documentation

Our Mark59 User Guide documentation can be found below:


Get 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

The name 'Mark59'

The 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.