Previous Topic: Extensions to JMeterNext Topic: Editing Test Files


Run a JMeter Test Case

To run a JMeter test case

  1. Verify that your CA IAM CS is running and that the endpoint referenced by the component test is functional. The core JDBC and SDK tests (run by ant jmeter.core) do not need external endpoints. The endpoint for the JNDI-related tests can be started externally using either ant -jcs.test.start.apacheds.lda or by running:
    jcs-sdk-home/build/dist/bin/apacheds_plain.bat
    
  2. In JMeter, click the node named View Results Tree and then select Run.

    Each test step is listed. To display results, click the result.

    If the test failed it, appears in red.

If an Equals tests on large test responses fails, cut-and-paste the expected and received lines of text to two lines of a temporary file. For example, a failure that occurs when comparing the entire results of a wide-ranging search request. Then, working backwards from the end, insert spaces in the shorter string until the later text realigns with the longer string. In this way, you can identify the sections where the two strings differ and verify that there is a logical reason for the differences. If you cannot find a reason, then debug the connector until the strings agree. Otherwise, cut-and-paste the response from the View Results Tree to the matching response assertion to record that this behaviour is now correct.

CA extensions to JMeter LDAP Extended Request Sampler, such as sort search results and the order of attributes within them, support such a stable textual comparison.

Stopping or restarting a test before it completes triggers different behavior on the next run due to created objects not being deleted at the end of the previous run. Therefore, only perform a final verification of response assertions for a test after the previous attempt has completed, so that all created objects are cleaned up.