What are WLE, BPM load testing best practices?

Answer

On Demand Consulting
Author: Andriy Melnyk

Common BPM load testing recommendations

• ?Understand your business goals. What must be achieved? ?For example, demonstrate that the BPM system meets a specific performance criteria.
• ?Define core business use cases to cover with performance testing.?
• ?Define complete, consistent, testable non-functional requirements.
• ?Define performance testing approach, for example: planning, scripting, test execution, results analysis and tuning, reporting
• ?Follow defined performance testing approach.

• ?It is not recommended to use the same user\password for multiple virtual users in the load testing script. Create unique users in the system. Use unique users to generate a workload.?? ?
• ?A typical BPM Portal workload is completing instances and tasks, also searching for data.
• ?Portal users execute a sequence of actions rather than one looped action. Don?t loop a request in the same user session multiple times serially unless this is a part of the business use case.
• ?Session cookies are used to identify user. Don?t clear cookies in a load test.
• ?Don?t hardcore cookies.
• ?Make scripts dynamic(parameterization and correlation):
• ?Support dynamic decisions
• ?Support dynamic data entry
• ?Use realistic think times(delays) between user actions

• ?Ensure test environment is correctly configured for metrics collection
• ?Apply tuning suitable to your current workload profile
• ?Turn off any active virus-scanning on load-generators, BPM servers and other hosts involved
• ?Start with a single user first. Make sure no errors exist with a single user.
• ?Warm up the system before a load test. You can use the same load test to warm up the system.
• ?Use reasonable level of monitoring, make sure monitoring doesn?t impact results.
• ?Tune the product properly if necessary. See public BPM Performance tuning guides for recommended tuning options.