We have developed Asp.NET application .It is automated Inventory Based System to place orders and shipped it to customer. There are no REST API. It contains UI and API layer. We need to do performance test using JMETER with 1000 users who will create inventory, create orders, create items, ship it to customer. We are doing feasibility study with JMETER. Using JMETER, I record Create Order workflow on FireFox. On UI, I performed 10-20 actions. These gets recorded in JMETER. However, for 20 actions, I can see more than 50 recorded HTTP requests. These are APIs which gets called internally.
Also, note that only record and play is not going to work. I need to store unique order Ids, read data from CSV etc. etc. So it requires lots of efforts also.
Is it recommended to do such performance test using JMETER. UI changes, flow changes or any change made by developer in code like JSON format, GET/POST data might affect my scripts ?