When to use JET, and when not to use JET

JET should be a good way to write your tests if:

• The product you want to test is distributed or has a client/server architecture
• It is natural for you to write the tests in Java
• You want invest time in developing tests and abstractions for later reuse

Distributed

JET will let you run tests on more than one machine, where the different machines can have different roles. If you do not need this functionality, maybe just using JUnit or similar would solve your need?

Tests in Java

JET is written in Java, and code that should be integrated into JET must be written in Java. The software under testing does not need to be written in Java, and we can start tests that are not written in Java (see the jet-example-memcached project for an example), but it will be much simpler with code that is written in Java.

Developed tests and reuse

The philosophy in JET is that you write your own abstractions and building blocks, and reuse them later. This means that there is an initial investment to get started, but we think that if you are going to run your tests many times, this will be a huge benefit later. If you are not willing to do an initial investment to structure your test building blocks, you should not use JET. There are some jet-example-* projects in the source code to give you a feeling of what is needed.