[PER-178] Sync Data and Reg Proc Performance Scripts

[akhilmoogi]

This PR contains performance scripts and support files for Sync data and Reg proc modules:

[nihallakshmankonchady]

@akhilmoogi
Script

• Naming of the samplers of Auth Token Generation Setup (Needs to be ended with Endpoint)

• Create Context Endpoint :

  • In payload body, we are hard-coding the secret value for regproc, can we call it from user-defined variables.
  • In payload body, we are hard-coding passoword partner_user_password, can we call it from user-defined variables
  • In payload body, we are hard-coding value for admin_zone_clientSecret, can we call it from user-defined variables
  • In payload body, we are hard-coding value for admin_zone_password, can we call it from user-defined variables
  • In payload body, we are hard-coding value for admin_userName, can we call it from user-defined variables
  • In payload body, we are hard-coding value for partner_userName, can we call it from user-defined variables
  • In payload body, we are hard-coding value for new_Resident_User, can we call it from user-defined variables
  • In payload body, we are hard-coding value for new_Resident_Password, can we call it from user-defined variables
  • In payload body, we are hard-coding value for mosip_resident_client_secret, can we call it from user-defined variables
  • In payload body, we are hard-coding value for AuthClientSecret, can we call it from user-defined variables
  • In payload body, we are hard-coding value for mosip_idrepo_client_secret, can we call it from user-defined variables
  • In payload body, we are hard-coding value for prereg.password, can we call it from user-defined variables
  • In payload body, we are hard-coding value for mosip_admin_client_secret, can we call it from user-defined variables
  • In payload body, we are hard-coding value for keycloak_Password, can we call it from user-defined variables
  • In payload body, we are hard-coding value for audit_password, can we call it from user-defined variables
  • In payload body, we are hard-coding value for pwd, can we call it from user-defined variables
  • In payload body, we are hard-coding value for mosip_reg_client_secret, can we call it from user-defined variables
  • In payload body, we are hard-coding value for user0, can we call it from user-defined variables
  • In payload body, we are hard-coding value for mosip_hotlist_client_secret, can we call it from user-defined variables
  • In payload body, we are hard-coding value for partner_password, can we call it from user-defined variables
  • In payload body, we are hard-coding value for machineName, can we call it from user-defined variables
  • In payload body, we are hard-coding value for userpassword, can we call it from user-defined variables
  • In payload body, we are hard-coding value for postgresql-password, can we call it from user-defined variables
  • In payload body, we are hard-coding value for mosip_pms_client_secret, can we call it from user-defined variables
  • In payload body, we are hard-coding value for mosip_testrig_client_secret, can we call it from user-defined variables
  • In payload body, we are hard-coding value for policytest_password, can we call it from user-defined variables
  • In payload body, we are hard-coding value for mosip.test.regclient.supervisorpwd, can we call it from user-defined variables
  • In payload body, we are hard-coding value for mosip.test.regclient.password, can we call it from user-defined variables
  • In payload body, we are hard-coding value for user2, can we call it from user-defined variables

• Create Persona Endpoint new remove "new" from the sampler name

• S02 Sync Data To The Server (Preparation) : Rename to Endpoint or to the query

• S03 Get Transaction Details From Reg Id (Preparation) -> Upload Registration Packet Endpoint -> Store Reg Id To File -> reg_id to regId

• ReadMe file is not updated as per the script.

[nihallakshmankonchady]

@akhilmoogi .
Script level

• For Auth Token Generation (Setup). We are not performing authentication but we are generating Auth token. Can you please rename it as Generate Auth token for Syncdata Endpoint.
• Packet Generation (Setup): Create Context Endpoint. I observe dev2 domain name in the payload. Can you please correct it.

[akhilmoogi]

Hi @nihallakshmankonchady I have changed the script as per your reviews.

[nihallakshmankonchady]

Reviewed

[nihallakshmankonchady]

@akhilmoogi
Approved from my end.

[nihallakshmankonchady]

@akhilmoogi

• S01 and S03 Sync Registration Packet And Generate RID (Preparation) --> and to And
• S01 and S03 Sync Registration Packet And Generate RID (Preparation) --> Do we need transaction controller -> Sync Registration Packet, Generate And Store RID ?
• S01 and S03 Sync Registration Packet And Generate RID (Preparation) --> Why are we placing Generate Packet Path From File under Sync Registration Packet Endpoint and Read Request Details From File under Read Request Details From File
• Update the Constant throughput timer value correctly for S01 Sync And Upload New Registration Packet (Execution), S02 Sync Data To The Server (Execution)
• Adding the dependent jar file details for the Syncdata for userpwd usecase

[nihallakshmankonchady]

All suggested changes are complete. @akhilmoogi I have reviewed the PR from my side. @vishwa-vyom Kindly review and merge the PR.