Skip to main content

Test Modules

Test Modules

General Information
The purpose of our test modules is to create a completely finished, plug and play style test template that can be merged into virtually any JMeter test. The goal is for NO additional configuration to be required to get these modules to work. To achieve this goal, we have a design philosophy behind every module that can be broken down into the following categories:

Modular Set Up
Endpoint Set Up
Endpoint Execution
Endpoint Tear Down
Modular Tear Down

Each module will contain any module specific information that it requires to run within it's own scope. Examples of this would be that the FileUploadModule will contain references to files that will be uploaded. Then, if a portion of the FileUploadModule will be required within a test, the module can be imported with any of the excess endpoints being disabled or removed altogether.

Structure
All of the Test Modules will consist primarily of Transaction Controllers with the "Generate Parent Sample" checked so that reports generated will be in a more convenient format.

The naming convention for the structure is as follows:

{ControllerName}Controller

  • Example: RoleController

{ControllerName}_SetUp

  • If any setup for this controller module to run across all steps needs to be done, it should be done in this Transaction Controller

{ControllerName}_{EndpointAction}

  • Example: Role_Add

{ControllerName}_{EndpointAction}_SetUp
Example: Role_Add_SetUp

  • If any setup is needed for this action to be able to succeed independently

{ControllerName}_{EndpointAction}_Execute

  • This is where the httpRequest to perform the action is run

{ControllerName}_{EndpointAction}_TearDown

  • This is where any clean up specific to this action is performed

{ControllerName}_TearDown

  • If there was any setup done that still needs to be cleaned up, it should be run in this step after all the Controller Actions have been performed.
Back to top