Pravesh wrote:
Hi Team,
How can we measure the rendering time in Jmeter for web apps, native apps &
API's ?
Morning,
When it comes to web applications, as per JMeter project main page
<https://jmeter.apache.org/>:
JMeter is not a browser, it works at protocol level. As far as
web-services and remote services are concerned, JMeter looks like a
browser (or rather, multiple browsers); however JMeter does not
perform all the actions supported by browsers. In particular, *JMeter
does not execute the Javascript* found in HTML pages. *Nor does it
render the HTML pages as a browser does* (it's possible to view the
response as HTML etc., but the timings are not included in any
samples, and only one sample in one thread is ever displayed at a time).
So even given you configure JMeter to behave like a real browser
<https://guide.blazemeter.com/hc/en-us/articles/206733719-How-to-make-JMeter-behave-more-like-a-real-browser>
and produce the same network footprint you won't be able to measure
"rendering" time because it's a feature of a real browser. If you need
that metric - consider using WebDriver Sampler
<https://jmeter-plugins.org/wiki/WebDriverSampler/> which provides
JMeter integration with Selenium <https://www.selenium.dev/> browser
automation framework.
The same applies to "native apps", JMeter can simulate network footprint
of the native app, but it won't give you "rendering" time, you will need
to integrate JMeter with desktop or mobile automation framework like
Appium <http://appium.io/>for this.
For APIs "rendering" term is not applicable, it's just a response to a
HTTP <https://developer.mozilla.org/en-US/docs/Web/HTTP> request so
request completion time is the elapsed time, no "rendering" is assumed.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org
