JUnit VS Gatling

Because I only wanna use the cmd java test, so I chose Junit4 which supports Plain-old JAR. I did test according to the Getting started document. But when I ran the javac -cp .:junit-4.XX.jar:hamcrest-core-1.3.jar CalculatorTest.java I got the error message CalculatorTest.java:4: error: package main does not exits. I tried to reorganize the folder and set Path according to others' experience 1, 2, but it still did not work.

Oops, another error. This is why we should read the manual 😅.

JUnit4

Delete those imports and remove the junit-jupiter-api dependency. Follow the instructions for JUnit 4.

Quite a lot of Java dependencies bring Junit 4 or Junit vintage engine as a transitive dependency.

The AHTest039.json file is the actual test. My testRunner() method (no relation to JUnit test runners) reads that JSON file, processes it, and asserts that the test passed. So my test class consists of a few Java methods, and what is essentially a list of JSON files to process.

Gatling: An open-source load and performance testing tool primarily designed for web applications, Gatling utilizes a simple domain-specific language (DSL) for creating and maintaining test scripts. It supports HTTP/2 and allows recording and generation of scenarios directly from a browser. The tool also provides detailed performance reports that are easy to analyze.

Performance and load testing are essential parts of GraphQL API testing. It ensures APIs can handle expected traffic volumes and respond within acceptable timeframes. You can use tools like Apache JMeter or Gatling to generate realistic loads and evaluate the API's performance under different scenarios. Techniques like batched queries and caching can help mitigate this issue.

New to the .NET community and trying to learn! I have used tools such as Apache JMeter (Java), gatling.io (Java) and Locust (Python) that are decent full featured web perf frameworks. Typically these integrate well with your code, and can be run as part of your unit/integration tests and produce offline reports

Gatling , this is what we tested concurrency with. Setting up might take a while depending on your exp. but the tool is solid.

I used SpringBoot 3.0.2, GraalVM 22 (JVM mode), a MacOS 2,6 GHz 6-Core Intel Core i7, running 1000 users for 5 minutes. The idea was to test how memory consumption and CPU usage evolve. Below, I compared the footprint of these three solutions. I collected the total count of requests, throughput, memory consumption, and CPU usage using VisualVM and Gatling.

Load test your code to simulate a production load (you can use tools like k6 or Gatling)

k6 is our preferred javascript based cloud tester for light webservices. gattling if you have (a monolith with) workflows and need more formalized code to prove/audit your testing.

It's read as "Ochikisu" and origin is the machine gun manufacturer Hotchkiss because this tool does not have as much firepower as the Gatling.