# Smoke-testing plugins during upgrade process

**URL:** <https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118>\
**Category:** Feature\
**Created:** [October 1, 2017, 8:18am UTC](https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118 "2017-10-01T08:18:48Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)\
**Post date:** [October 2, 2017, 12:46am UTC](https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118/7 "2017-10-02T00:46:32Z")

</div>

I would propose something simple in the way WordPress / WooCommerce does it…  
… no mythical perhaps complex smoke tests…

This blog post outlines the recent introduction specifically for WooCommerce related plugins:

> **[Private Site](https://woocommerce.wordpress.com/2017/08/28/new-version-check-in-woocommerce-3-2/)**

When an upgrade check is performed Discourse could advise / give helpful warnings to prevent plugin related errors that could lead to broken features / downtime.

A plugin predefined file should contain two Discourse version number values:

- “Requires at least”
- “Tested up to”

“Tested up to” Discourse version number which indicates the version of Discourse the developer of the plugin has tested the plugin against.

The blog post goes into benefits of requiring the plugin developer to update this version number and ultimately reducing the immediate work required by the plugin developer to update the plugin because the user is warned prior to upgrade.

---

_[View the full topic](https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118)._