CloudMeter

Introduction

This is an attempt to port the Apache Jmeter project to a Spring web application.

The reasons and design goals for this endeavor are:

• Distributed Architecture
  • JMeter already runs distributed tests, but in a large organization it's hard to share testplans or compute resources to run them.
  • CloudMeter is entirely distributed so everyone can access testplans (given access roles), schedule tests to be run on available resources, store and share results easily.

The end goal for this layout would look something like this: Users connect throw a web browser to a cloud-meter server (either locally or clustered across a network). They store testplans in a repository (relational-database, etc.,). Given a permission/directory structure other users may then interact with other users test plans. Distributed test runs behave much like they do in the Apache project.

Disclaimer

This project is still in the very beginning stage of development, meaning if you happen to be reading this you're probably about 4 years early. It does not work. It may do very little other than boot and it may not even do that.

I can make no guarantees about the working state of this project or the code. If it's here, it compiles, but that's about it at this time. I intend to be working on it a lot in the future and this README will change as the maturity of this project increases.

Current Status

Also refer to the wiki

Right now I'm working a lot on building out the /api/v1/testelement api.

This will enable users to create new items in the ui.

At this moment (at least when I'm working on the ui) I'm mostly working on the static html pages so I can modify the frontend js and simply refresh my browser without having to recompile the jar.

What's next

• Once the testelement api is complete, the js frontend needs to be updated to interact with it fully At which point, you should be able to build out a tree on the left hand side.
• Then, the all the center-right screen needs to show text fields, areas, check boxes etc to actually update and interact with the elements themselves.
• Then comes storage. Once we can interact with test plans, we'll need to be able to store
• By the time that happens, I'm sure I'll have this list updated so I don't really have to finish it now.