Production System Smoke Test

Modifications, code fixes and configuration changes to production systems are a necessity on a software implementation project. A formal testing procedure is recommended when major changes are made, but sometimes testing is minimized for smaller changes. Unfortunately, small changes can also lead to system outages and user frustration if not properly vetted or if key startup procedures are missed. Systems today are so complicated that even simple fixes can break existing functionality due to a relationship not documented or not completely understood.

One way of mitigating the risk of outages caused by minor changes is to develop a standard production system Smoke Test.  This smoke test should be performed after any change is made, but before all the users are given general access to the system. It would be ideal if the person performing this smoke test was independent of the group that had made the change or was not the group that stayed up all night long resolving the problem.

Generally, smoke testing happens after formal testing, but in the case of minor system changes, formal testing may be considered unnecessary. The use of a “smoke test” in this case gives the systems group an early warning to issues that might easily be addressed before full production is resumed. Provided below are some examples of the tasks to be included in the standard smoke test.

Standard Smoke Test Tasks:

1. Validate essential business processes

For example:

  • Perform a sales order from Quote to Cash
  • Perform the procure to pay cycle
  • Do an inventory transaction

2. Validate essential system interfaces

For example:

  • Run a sample credit card transaction
  • Test out a transaction using the tax interface
  • Test out EDI interfaces
  • Run a workflow
  • Test an alert
  • Run a batch job and have it send out an email
  • Verify the help functionality works
  • Test the enterprise portal

3. Validate essential peripheral devices

For example:

  • Run reports in batch and print them
  • Check inventory using a hand-held device

In summary, a Smoke Test is a good practice to ensure that essential system functionality is validated after any change. The result should be more productive users and less system frustration.


Related Posts


  1. Rosie Beckett

    You make a great point that you should have a standard smoke control test after making any changes to the structure or networks of your office. Also, it would give me peace of mind to have a third party perform the smoke test and is independent of the group that made the changes. My husband’s work is thinking of making some changes in the office and I will make sure to share these benefits of smoke system testing with him.

  2. Taylor Valnes

    Hello Rosie,

    Thank you for your comment, and for sharing this information with others!


Submit a Comment

Your email address will not be published. Required fields are marked *

Upcoming Events


31mar01aprTraining Class: Financial Reporting W/Account Schedules for Dynamics 365 Business Central

07apr2:00 pm2:30 pmEnsuring Quality for Batch Manufacturers

08apr11:00 am12:00 pmConfab with Stoneridge - Livestream - Jumping into the Deep End of the Data Lake

14apr10:00 am10:30 amBoost Seller Productivity and Close More Business with Dynamics 365 Sales

21apr10:00 am10:30 amSetting Your Sales Team Up for Success: A Modern Look at Revenue Operations

21apr12:00 pm1:00 pmGetting Started with Barcode Scanners and WMS Apps for Business Central

21apr2:00 pm3:00 pmMoving to the Cloud: Today's Solution for Leading Field Service Companies

22apr11:00 am12:00 pmConfab with Stoneridge - Livestream - Moving from Manual to Automated with Strategic Automation Strategies

28apr10:00 am10:30 amThe Modern Manufacturer: Best Practices for Inventory Turnover

28apr12:00 pm1:00 pmPower Up Microsoft Dynamics by Automating Budgeting, Dashboarding and Reporting


05may10:00 am10:30 amAchieve More with Zetadocs for Business Central

05may2:00 pm2:30 pmSimplifying Item Pricing, Availability, and Tracing for Batch Manufacturers

06may11:00 am12:00 pmD365 Field Service – New Features to Empower Your Remote Workforce

12may10:00 am10:30 amThe Modern Manufacturer: Manufacturing Software in the Real World

12may12:00 pm12:30 pmFinancial Implications of Moving from Dynamics GP to Dynamics 365: Licensing and Infrastructure

17may(may 17)8:00 am28(may 28)11:00 amDynamics 365 Finance & Supply Chain Development Training - Online Workshop

26may10:00 am10:30 amThe Modern Manufacturer - Enterprise Asset Management

About Stoneridge
Stoneridge Software is a unique Microsoft Gold Partner, with emphasis on partner. With specialties in Microsoft Dynamics 365, Microsoft Dynamics AX, Microsoft Dynamics NAV, Microsoft Dynamics GP and Microsoft Dynamics CRM, we focus on attracting the most knowledgeable experts in the field to our team, and prioritize delivering stellar solutions with maximum impact for your business. At Stoneridge, we are deeply committed to your results. Each engagement is met with a dedicated team, ready to provide thorough, tailored, and expert service. Based in Minnesota, we intentionally “step into your shoes,” wherever you are. We focus on what you care about, and develop trusting, long-term relationships with our clients.

Subscribe To Our Blog

Sign up to get periodic updates on the latest posts.

Thank you for subscribing!