The Value of End-User Testing

Why Comprehensive End-User Testing Matters

I've been in the ERP business for over 25 years, and one thing I've learned is that end-user testing is often overlooked or minimized, which can be a big mistake. It's like that car parts company slogan, "Pay me now or pay me later." When it comes to a smooth go-live cutover, I couldn't agree more. Comprehensive end-user testing is key to making sure a Business Central rollout goes off without a hitch. Drawing from my early days working for Solomon partner, I'll share a method for creating effective unit, process, and enterprise test scripts, including how to use the Business Central scripting tool. But first, why does comprehensive end-to-end testing matter? 

Ensures System Functionality: End-user testing verifies that Business Central functions as intended in real-world scenarios. It helps identify any issues or gaps that the team might have missed.

Enhances User Adoption: When end-users are involved in testing, they become more familiar with the system, which increases their confidence and willingness to adopt the new solution.

Reduces Risk: Comprehensive testing mitigates risks by uncovering potential problems before the system goes live. This prevents costly disruptions and ensures a smoother transition. 

Improves System Quality: End-user testing helps improve the overall quality and reliability of Business Central by simulating actual business processes.

Methodology for Unit, Process, and Enterprise Test Scripts

Unit Testing

Definition: Unit testing involves testing individual components or functions of Business Central to ensure they work correctly in isolation. These are generally the most basic data elements in Business Central.

Methodology: 

• Identify Units: Determine the system's smallest testable parts, such as functions, procedures, or modules.
• Create Test Cases: Develop test cases that cover all possible scenarios for each unit. Include both positive and negative test cases.
• Execute Tests: Check your work and record the results. Fix any issues identified during testing

Example: Validating item creation. Of course, there are required fields, and the test script should identify those and provide information to guide a user in making the proper choices. Assume you are creating a new Finished Good Production item, and the finance team needs to select the proper Inventory Posting Group along with all the other necessary fields. With our test script, we guide the user through the steps required and provide clues on choices that they need to make.

Process Testing - More Comprehensive Steps

Definition: Process testing involves testing end-to-end discrete processes. 

Methodology: 

• Define Processes: Identify key business processes that need to be tested, such as entering a sales order or processing a warehouse receipt.
• Develop Test Scenarios: Create realistic test scenarios that simulate actual business operations. Include all relevant steps and interactions and, if appropriate, sample data. The testing validation lives at the scenario level and not beyond the process test.
• Create Test Scripts: Write detailed test scripts that outline the steps to be performed during testing. Ensure the scripts cover all possible variations of the process. This point is key. If you sometimes ship multiple orders on the same shipment, be sure that the requirement is included in the script. A single order may not produce the same results.
• Execute Tests: Perform the tests and document the results. Address any issues or discrepancies found during testing.

Example: Testing sales order entry for existing customers where special pricing exists.

Using Business Central's Scripting Tool for Process Testing

Business Central includes a powerful page scripting tool that can automate process testing by recording and replaying user interactions within the web client. Here's how you can use it:

• Start Recording: Open the page where you want to start recording. Select the Settings icon > Page Scripting > Start new recording. Perform the task you want to record.
• Replay Recording: Once recorded, you can replay the interactions to validate system behavior. This helps ensure the process works as expected after changes or updates.
• Save and Share: Save the recordings for consistent testing across different teams.
  
  These saved recordings can then be used when something changes in the system, such as a required update or ISV installation.

Enterprise Testing

Definition: Enterprise testing involves testing complete processes like the order-to-cash process, which includes order entry, inventory management, shipping, invoicing, and payment processing. The test scripts would cover each step and interaction within the process. Unit and Process test scripts have already been developed to provide the basis for the processes under test. In the Enterprise, the team is looking at everything.

Methodology: 

• Plan Tests: Develop a comprehensive testing plan that includes all employed modules and functionalities of Business Central.
• Create Test Scenarios: Design test scenarios that cover the full scope of Business Central, including integrations with other systems and external interfaces.
• Develop Test Scripts: Write detailed test scripts that guide testers through the entire system, ensuring all functionalities are tested.
• Execute Tests: Conduct the tests and record the results. Resolve any issues identified during testing.

Example: Testing Business Central for a manufacturing company, including modules for production planning, inventory management, procurement, sales, and financial reporting. The test scripts would ensure that all modules work together seamlessly and meet business requirements.

Do I define a process that takes a lot of work and time? Yes, but back to "pay me now or later." As employees leave, systems update, or changes are made, being able to fall back on these scripts will save time and money in the care and feeding of Business Central in the long run and reduce the risk of a problematic go live.