简体   繁体   English

Selenium Webdriver + Jmeter + StormRunner 进行性能测试

[英]Selenium Webdriver + Jmeter + StormRunner for Performance test

I wanted to try out integration of Selenium Jmeter and StormRunner.我想尝试集成 Selenium Jmeter 和 StormRunner。 My end goal is to do Load testing with 'n' number of users on StormRunner What?我的最终目标是在 StormRunner 上对“n”个用户进行负载测试什么? - For eg I have Selenium Script, convert it in to Jmeter (I can get this information from many sources) Then my Jmeter script should get ready Then upload Jmeter script in to StormRunner and pass the necessary parameter through Jenkins and run the load test. - For eg I have Selenium Script, convert it in to Jmeter (I can get this information from many sources) Then my Jmeter script should get ready Then upload Jmeter script in to StormRunner and pass the necessary parameter through Jenkins and run the load test.

I really want the opinion here about feasibility and whether it is in right direction or not.我真的很想在这里就可行性以及它是否朝着正确的方向发表意见。 Idea here is that Automated Load/Performance test这里的想法是自动负载/性能测试

Selenium is a browser automation framework and JMeter acts on HTTP protocol level so your "Automated" requirement might not be fulfilled especially if your tests are relying on client-side checks like sorting or waiting for element to appear. Selenium是一个浏览器自动化框架,JMeter 作用于HTTP 协议级别,因此您的“自动化”要求可能无法满足,特别是如果您的测试依赖于客户端出现排序。

Theoretically given you properly configure JMeter it can behave like a real browser , but it still not be executing client-side JavaScript.从理论上讲,如果您正确配置 JMeter,它可以像真正的浏览器一样运行,但它仍然不能执行客户端 JavaScript。

If you're fine with this constraint - your approach is valid, if not and the "automated functional test" requirement is the must - consider migrating to TruClient Protocol instead如果你对这个限制没意见 - 你的方法是有效的,如果不是,并且“自动功能测试”要求是必须的 - 考虑迁移到TruClient 协议

Why wouldn't you covert your script to a native Loadrunner/Stormrunner form of virtual user?为什么不将脚本转换为虚拟用户的原生 Loadrunner/Stormrunner 形式?

You should look at the value of what you are trying to achieve.你应该看看你想要达到的价值。 The end value of a performance test is in analysis.性能测试的最终价值在于分析。 Analysis simply takes the timing records and the resource measurements produced during the test, bringing them together on a common timestamp, and then allowing you to analyze what resource "X" is being impinged when timing record "Y" is too long.分析只是获取测试期间产生的计时记录和资源测量值,将它们放在一个公共时间戳上,然后当计时记录“Y”太长时,您可以分析哪些资源“X”受到影响。 This then points to some configuration or code which locks up on resource, "X."然后,这指向锁定资源“X”的某些配置或代码。

What is your path to value in your model?您在 model 中实现价值的途径是什么? You speak about converting a functional test script to a performance one.您谈到将功能测试脚本转换为性能测试脚本。 Realistically, you should already know that your code, "works for one," before you get to asking, "Does it work for many?"实际上,您应该已经知道您的代码“适用于一个人”,然后再问“它适用于许多人吗?” There is a change in script definitions which typically accompanies this understanding.通常伴随这种理解的脚本定义会发生变化。

Where are your collection of resources noted?您的资源集合在哪里注明? Which Resources?哪些资源? On which Hosts?在哪些主机上? This is on the "path to value" problem where you need to have the resource measurements to diagnose root cause of poor performance.这是关于“价值之路”的问题,您需要通过资源测量来诊断性能不佳的根本原因。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM