By Phil Coulthard

Before going into production, ensure that you planned for and tested non-functional aspects of your process, including response time of the user interface, throughput, and scalability. Allot adequate time for this phase before going to production. The test environment should match the target production system as closely as possible, and the use cases should represent both typical and stress scenarios that are anticipated in production. All systems should be tuned according to the IBM BPM Performance Tuning redpaper guidelines before you perform the non-functional tests.

Applicable editions: Express, Standard and Advanced

Applicable releases: All

Source: IBM

1 comment on"Good practice – Plan for and perform non-functional testing"

  1. […] Plan for and perform non-functional testing […]

Join The Discussion

Your email address will not be published. Required fields are marked *