It is crucial that load tests are conducted with a specific and realistic performance and load target in mind.
Performance goals can be determined by analyzing the execution time of individual actions. For instance, if saving a sales order takes 10 seconds per save, and you plan to save 1,000 sales orders, then the estimated duration of the test would be 10,000 seconds or 2 hours and 45 minutes.
The number of concurrent threads should adhere to concurrency governance guidelines. To ascertain the available concurrency, refer to your service tier and SuiteCloud licenses.
Increasing concurrent threads may not necessarily lead to a linear increase in throughput. Concurrent resource access can impact overall performance.
Test data should accurately reflect live data and usage patterns. It should also consider the normal variations expected in production data. Avoid using a single customer or item for testing. For example, when testing the customer payment process, ensure the following:
– Vary the customer details.
– Vary the payment types.
– Vary the number, type, and quantity of order lines.
– Test order and order line customization.
The testing environment should closely resemble the production setup to yield representative results.
Load tests should be conducted iteratively. Test, analyze, make necessary adjustments, and retest. Repeat this process.
Utilize the Application Performance Monitor to assess your testing procedures.
Inform NetSuite Customer Support about any upcoming load tests by submitting a support case. Include the following details:
– Authorized contact person for notifications.
– Account type and ID where testing will take place.
– Date, time, and duration of the test.
– Features or functionalities being tested.