<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Easytest on ZeroSharp</title><link>https://www.zerosharp.com/blog/categories/easytest/</link><description>Recent content in Easytest on ZeroSharp</description><generator>Hugo</generator><language>en-gb</language><copyright>Copyright © 2012–{year} Robert Anderson</copyright><lastBuildDate>Mon, 22 Apr 2013 16:31:00 +0100</lastBuildDate><atom:link href="https://www.zerosharp.com/blog/categories/easytest/index.xml" rel="self" type="application/rss+xml"/><item><title>Load Testing XAF: Bonus - Simultaneous EasyTests</title><link>https://www.zerosharp.com/load-testing-xaf-bonus-simultaneous-easytests/</link><pubDate>Mon, 22 Apr 2013 16:31:00 +0100</pubDate><guid>https://www.zerosharp.com/load-testing-xaf-bonus-simultaneous-easytests/</guid><description>&lt;p&gt;In &lt;a href="https://www.zerosharp.com/load-testing-xaf-overview"&gt;my recent series on load testing XAF&lt;/a&gt;, I used a Selenium javascript test to run the client browser instances. This is a good and cheap method of validating the performance of XAF applications under production load.&lt;/p&gt;
&lt;p&gt;However, if the load tests fail because of a concurrency bug or a performance bottleneck, it can still be difficult to analyse and solve. For this, we need to be able to simulate load locally against the development environment.&lt;/p&gt;</description></item></channel></rss>