Posted by Albert Gareev on Aug 22, 2012
Parent page: Load/Performance Testing with NeoLoad Providing irrelevant or misleading test results is worse than not providing test results at all. When using automation, testers must be twice as careful about relevance of tests – or maybe ten more times, hundred times – depending on how much judgment is passed on to mindless side. Load […] ...
Posted by Albert Gareev on Aug 15, 2012
Parent page: Load/Performance Testing with NeoLoad Load scripts are typically linear: they’re intended to generate a load, not to cover sophisticated logical scenarios checked by functional automation and explored by skilled testers. For this reason, load scripts rarely contain complex code branches and loops. Yet there are functional scenarios that are part of the load, […] ...
Posted by Albert Gareev on Aug 08, 2012
Parent page: Load/Performance Testing with NeoLoad Although recording is necessary phase in creation of load scripts, I prefer constructing my own modules based on results of reverse engineering analysis of captured client/server communication. Partially because this way I create reusable structures with containers, partially because I want to control setting of think time and pacing, […] ...
Posted by Albert Gareev on Aug 06, 2012
Some time ago I had a hard time discussing performance problem with application developer. My challenge was to overcome a “block” set by the developer: “this is a one-page code, it’s a very simple logic, and I see no reasons to spend time evaluating its performance”. I didn’t have more than 5-7 minutes for the […] ...
