Using Groovy in JMeter: Demos, Context Access, and Throughput Insights
The article shares a series of JMeter demos that leverage Groovy for accessing the test context, retrieving SampleResult and previous sampler data, discusses the limited usefulness of thread scheduling via Groovy, highlights a discovered throughput discrepancy, and provides practical advice and links to related technical resources.
Initially unfamiliar with JMeter, the author discovered that JMeter has long supported Groovy, which sparked the creation of a demo and an article; since then, multiple demos beyond the basic ctx and script file usage have been completed.
The ctx object enables access to higher‑level information such as SampleResult or prev. Although official documentation mentions thread scheduling features for interrupting threads or loops, the author finds the built‑in JMeter thread management more practical, so the Groovy experiments in JMeter conclude here.
An accidental observation of a theoretical throughput discrepancy in JMeter leads the author to offer two recommendations: consult official or community documentation frequently, and engage in discussions with peers to explore solutions.
The page then lists the complete set of JMeter‑focused articles, covering topics such as handling assertions and logs with Groovy, manipulating variables, executing command lines, processing request parameters, using regex extraction, managing cookies and headers, and analyzing throughput errors.
A disclaimer notes that the original article was first published on the "FunTester" public account and that redistribution (except by Tencent Cloud) is prohibited.
Additional curated technical articles are presented, including resources on Linux performance monitoring (netdata), performance‑testing frameworks, command‑line performance testing, HTTP mind maps, visualizing test data, measuring asynchronous API latency, and multi‑login performance strategies, as well as non‑code pieces on programming mindset, JSON basics, tester self‑improvement, automation pitfalls, full‑stack automation engineering, and the debate between manual and automated testing.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
