{"id":30450,"date":"2024-01-25T16:41:55","date_gmt":"2024-01-25T15:41:55","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=30450"},"modified":"2024-09-10T17:59:25","modified_gmt":"2024-09-10T15:59:25","slug":"load-test-m-files-server-with-jmeter","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/load-test-m-files-server-with-jmeter\/","title":{"rendered":"Load Test M-Files Server with JMeter"},"content":{"rendered":"\n

Creating load test scenario on a web application might look easy:<\/p>\n\n\n\n

    \n
  1. Record a scenario<\/li>\n\n\n\n
  2. Replay it<\/li>\n<\/ol>\n\n\n\n

    In practice, it is much more complex than that when you want to manage variables elements like usernames, session IDs, and, in case of M-Files, a Vault ID.<\/p>\n\n\n\n

    Also, JMeter does not manage client-side java script and, if application requires it, you must “emulate” it with some code. Luckily, JMeter can run code with JSR223 Sampler. This requires coding skills to understand what the application does with help of Web Developer Tools<\/em> provided with your favourite browser.<\/p>\n\n\n\n

    The first scenario will look like this:<\/p>\n\n\n\n

      \n
    1. Login<\/li>\n\n\n\n
    2. Search<\/li>\n\n\n\n
    3. Select first element in the result page<\/li>\n\n\n\n
    4. Thinking time<\/li>\n\n\n\n
    5. Logout<\/li>\n<\/ol>\n\n\n\n

      Recording<\/h2>\n\n\n\n

      To record, I need a simple scenario with one Thread group<\/em> with a Recording Controller<\/em> and a HTTPS Test Script Recorder<\/em> with a View Results Tree<\/em> listener. When record is done, you will end up with something like this (a transaction controller for each named steps and as many HTTP request as recorded):<\/p>\n\n\n\n

      \"\"<\/figure>\n\n\n\n

      Variables<\/h2>\n\n\n\n

      Search and Find<\/h3>\n\n\n\n

      First job is to find what are the variable parts of these queries. Before that, you must have the following Managers defined:<\/p>\n\n\n\n