Apache JMeter VS TestNG

The test scenario consists of querying for descriptions of different offers. During the test, I will collect data on memory and GC parameters using jConsole. I will run the test scenario using jMeter, which additionally will allow me to measure response times.

FYI some of our people internally use Jmeter. https://jmeter.apache.org/

It's not flashy so it probably wont get the standard "we are going to milk you for data" plan

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.

JMeter

Improving just one endpoint and a database query does not guarantee we can handle the load we are expecting. One effective tool for load testing is Apache JMeter, which can simulate multiple users accessing and making requests to the system simultaneously.

Apache Jmeter https://jmeter.apache.org/ but I can't drop my infra and I have Java socket closed errors

Good morning what tool do you use to test your infra in terms of http load ? A tool that works, I tested : - https://github.com/tsenart/vegeta but it returns 0 errors or a http_net error from Golang - LOIC (Low Orbit Ion Canon) https://github.com/NewEraCracker/LOIC but the requests do not appear in my nginx logs and I feel no slowdown - Apache Jmeter https://jmeter.apache.org/ but I can't drop my infra and I have Java socket closed errors - K6 https://k6.io/ but I can't bring down my infra with - wrk https://github.com/wg/wrk no matter what parameter I put it doesn't make enough requests per second, I put the same parameters as on a tutorial and I don't get the same result...

I think the apache program sites all give similar vibes, and they are used alllllllllllll the fuck over, even if ppl don't realize it. Apache libraries and tools are great. Jmeter is still the choice for a lot of load testing efforts, and it's site looks like this: https://jmeter.apache.org/

JMeter is a well-known tool for load or stress testing, it basically sends requests to your application within the given time, according to the behaviour plan you provided. The plans are designed to be detailedly configurable and focused on load-testing jargon. That makes the JMeter a comprehensive solution, however makes it a bit hard to understand & focus on the well written tests.

We set up staging environments in AWS to test our new infrastructure. Starting with some relatively modest capacity choices (1-2 t3.small instances per web app), we performed load tests on the most popular pages on each site. We built some simple load testing scripts that wrapped Apache JMeter commands:

Testing tools on the JVM stopped using reflection about twenty years ago, they all use annotations these days (e.g. https://testng.org, https://junit.org). Rust has annotations too, obviously.

Recently though we've run across a few issues with the asserts in TestNG. In 7.3.0, some changes broke assertSame/assertNotSame that also broke some of our tests. This was partially fixed in 7.4.0, but some overloads of assertEquals were still broken. This is fixed, but I don't think the fix has been delivered in a release yet. Further investigation revealed that at least one overload of assertNotEquals has been broken, apparently since 6.9.5 or even earlier.

TestNG is a Java-based open-source testing framework. The framework is inspired by JUnit and NUnit. You can also create an HTML report during testing implementation.