A Blog About Automated Testing in NetSuite
BOSTON, MA, APRIL 19, 2018 – Xcelero today announced it will be a Silver sponsor at SuiteWorld18, an annual celebration of NetSuite customers and partners. Now in its 8th year, SuiteWorld is the preeminent Cloud ERP conference where users,...
The Rocky Mountain NetSuite User Group held a meeting on May 18th, 2017 in Denver CO. It was a very well attended event with over 100 participants. Xcelero was a proud sponsor of the event. Karan Karandikar, CTO made a...
Mimecast presented their case study in using Xcelero at SuiteWorld 2017 in Las Vegas. The presentation is now available in SuiteAnswers - Answer Id: 64104
We are constantly rolling out new customizations in support of business initiatives in our NetSuite environment. Recently, we were in the process of introducing a complex approval process with over one hundred possible business scenarios that needed to be tested. With Xcelero, we were able to rapidly capture test data, define pass/fail criteria and automate execution. It was a big time saver. We were also able to leverage Xcelero for our 2017.1 Release Preview testing.
We have a complex and highly customized NetSuite environment and need to test hundreds of test cases. When we were testing manually, it would take our QA Analyst an average of one day to define and document six test cases in Microsoft Excel. Execution, verification and documentation of these six test cases would take roughly three hours for every test cycle. This translated into hundreds of hours spent in testing. (more…)
All users of ERP applications would readily admit to this: There would be a lot more testing if it wasn’t so tedious. Why is testing so difficult? For starters, you need a test plan. Next, each scenario to be tested needs to be identified. Then, expected results need to be defined. If the use case required a process flow to be tested, one use case scenario may involve multiple test cases.
In short, Business Process Validation refers to the process of identifying business scenarios to be tested, creating test scripts to reflect the same, executing these test scripts methodically and analyzing results.