Skip to main content
Question

Environment performance issues

  • September 24, 2026
  • 6 replies
  • 84 views

Hello Team,

I hope you are doing well.

I would like to raise a concern regarding the performance and stability of the Acumatica sandbox environment. As an Automation QA Engineer, I have been experiencing significant issues that are impacting our automation testing efforts.

One of the main challenges is the inconsistent and unstable page load times. The environment's performance varies considerably, which affects the reliability of our automated regression test executions and often causes test failures.

In addition, we have noticed that UI element locators are not stable and frequently change or become unreliable. As a result, our automation scripts require continuous updates and daily maintenance to keep the test suite functional. This consumes a significant amount of time and effort that could otherwise be focused on expanding test coverage and improving quality.

I would also like to note that these issues have been present in both the previous sandbox environment and the newly upgraded version, which suggests that the concerns may not be related to a specific release.

Could you please let us know if there is a known cause for these performance and locator stability issues? Additionally, are there any recommendations, configuration changes, or best practices that could help improve the environment's stability and make it more suitable for automation testing?

Your guidance and support would be greatly appreciated.

Thank you for your time and assistance.

6 replies

DasunPerera91
Acumatica Employee
Forum|alt.badge.img+2
  • Acumatica Employee
  • September 26, 2026

Hi ​@alya 

Generally, free sandboxes are intended for functionality testing not for performance, they are not allocated the same resources as production instances. If the client needs to have a sandbox with the same resources this would need to be paid.


mohammadnawaz51
Varsity I
Forum|alt.badge.img+8

​@alya Which version you are working on sandbox testing, if 26r1 there is an issue with performances and acumatica working on it for the permanent fix.

 


Steve Milner
Varsity III
Forum|alt.badge.img+4
  • Varsity III
  • September 28, 2026

@alya Dasun and Mohammad covered the performance side. For the locators, Acumatica publishes its own UI test framework, the Test SDK, and Acumatica's starter guide is the place to start:
https://github.com/Acumatica/Test-SDK-Starter-Guide

It's C# on top of Selenium, but you don't maintain locators by hand. A wrapper generator reads the screens you list and writes a page class for each, so a test line looks like this:

SOOrderEntry.Document.CustomerID.Type("AACUSTOMER");

The element IDs live in the generated code. When the build or a customization changes, you regenerate the wrappers and the IDs update in one place.

For the load times, it has smart delays built in. Buttons that start a long-running operation wait for it to finish by default, and the SDK checks that a button or box is visible and available whenever it clicks or enters data.

There's a Test SDK for every build, in the TestSDK folder next to the installer on builds.acumatica.com, and its packages have to match the version of the site you test. Classic UI wrapper generation needs the site's install folder, so you'd run it on a local install of the same build with your customization projects published. It edits that site's web.config while it runs, so let it finish. On 26 R1, wrappers for Modern UI screens are generated differently, and this thread has a working setup:
https://community.acumatica.com/isv-solutions-116/modern-ui-support-in-2026r1-testsdk-34468


  • Author
  • Freshman I
  • September 30, 2026

​@DasunPerera91,

We are performing functional testing. I meant that the inconsistent loading times are affecting the test runs and causing instability in the automation. Thank you.


  • Author
  • Freshman I
  • September 30, 2026

mohammadnawaz51,

Currently we are using 26-1, but I’ve been experiencing this issue  since the previous version of Acumatica. Thank you.


  • Author
  • Freshman I
  • September 30, 2026

Steve Milner, 
Currently, we’re using Cypress with Typescript. Do you think this could be the issue? And if we move to the Acumatica Test SDK, would we still need to upgrade the Sandbox, or can the SDK work with our current sandbox? Thank you.