PaperCut Post Upgrade Test Plan

KB Home   |   PaperCut Post Upgrade Test Plan

Main.PostUpgradeTestPlan History

Hide minor edits - Show changes to output

July 12, 2016, at 12:51 PM by rossm - future proofed the printable view link wordage
Changed line 5 from:
The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.  It is advisable to print out this page (''Printable View'' link is in the menu on the left) and check off the steps as the tests are performed.
to:
The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.  It is advisable to print out this page by selecting the ''Printable View'' link and checking off the steps as the tests are performed.
Changed lines 5-6 from:
The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.  It is advisable to print out this page (''Printable View'' link is on the left) and check off the steps as the tests are performed.
to:
The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.  It is advisable to print out this page (''Printable View'' link is in the menu on the left) and check off the steps as the tests are performed.
Changed lines 5-6 from:
The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.  It is advisable to print out this page (''Printable View'' link above) an check off the steps as the tests are performed.
to:
The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.  It is advisable to print out this page (''Printable View'' link is on the left) and check off the steps as the tests are performed.
Changed line 7 from:
* Verify that administrators (e.g. the build in [@admin@] user) can log into the interface at
to:
* Verify that administrators (e.g. the built-in [@admin@] user) can log into the interface at
Changed lines 8-9 from:
-->[@http://servername:9191/user@]
to:
-->[@http://servername:9191/admin@]
Changed lines 19-20 from:
* Verify that end-users can log into the end-user web interface at '''[=http://servername:9191/user=]'''.  e.g. use a test account to verify this.
to:
* Verify that end-users can log into the end-user web interface at [@http://servername:9191/user@].  e.g. use a test account to verify this.
Changed lines 1-2 from:
(:title PaperCut Post Upgrade Test Plan :)
to:
(:title PaperCut Post Upgrade Test Plan:)
Changed lines 42-44 from:
* Take some time to explore and play with any new features!  The [[https://www.papercut.com/release_history/ | release history]] page is a good place to start to gain a quick overview of what's new.  Also check out the [[KnownIssues|known issues]] list for any important notes associated with this release.  Generally [[https://www.papercut.com/|print management software]] is pretty run-of-the-mill but we try and slip in an exciting feature in PaperCut from time to time!

[-keywords: testing, upgrade, update, procedure -]
to:
* Take some time to explore and play with any new features!  The [[https://www.papercut.com/release-history/ | release history]] page is a good place to start to gain a quick overview of what's new.  Also check out the [[KnownIssues|known issues]] list for any important notes associated with this release.  Generally [[https://www.papercut.com/|print management software]] is pretty run-of-the-mill but we try and slip in an exciting feature in PaperCut from time to time!
Changed line 45 from:
''Categories:'' [[!Administration]], [[!Upgrading]]
to:
''Categories:'' [[Category.Administration|+]], [[Category.Upgrading|+]]
Added line 47:
[-Keywords: testing, upgrade testing, update, test procedure-]
Changed lines 42-43 from:
* Take some time to explore and play with any new features!  The [[https://www.papercut.com/products/ng/release_history/ | release history]] page is a good place to start to gain a quick overview of what's new.  Also check out the [[KnownIssues|known issues]] list for any important notes associated with this release.  Generally [[https://www.papercut.com/|print management software]] is pretty run-of-the-mill but we try and slip in an exciting feature in PaperCut from time to time!
to:
* Take some time to explore and play with any new features!  The [[https://www.papercut.com/release_history/ | release history]] page is a good place to start to gain a quick overview of what's new.  Also check out the [[KnownIssues|known issues]] list for any important notes associated with this release.  Generally [[https://www.papercut.com/|print management software]] is pretty run-of-the-mill but we try and slip in an exciting feature in PaperCut from time to time!
Changed lines 42-43 from:
* Play with any new features!  You may wish to now take some time to explore any new features.  The [[https://www.papercut.com/products/ng/release_history/ | release history]] page is a good place to start to gain a quick overview of what's new.  Also check out the [[KnownIssues|known issues]] list for any important notes associated with this release.
to:
* Take some time to explore and play with any new features!  The [[https://www.papercut.com/products/ng/release_history/ | release history]] page is a good place to start to gain a quick overview of what's new.  Also check out the [[KnownIssues|known issues]] list for any important notes associated with this release.  Generally [[https://www.papercut.com/|print management software]] is pretty run-of-the-mill but we try and slip in an exciting feature in PaperCut from time to time!
Changed lines 38-39 from:
* If PaperCut is running on top of an external database system (e.g. Microsoft SQL Server, MySQL, etc.), verify that your off-disk backup procedure includes the host database.
to:
* If PaperCut is running on top of an external database system (e.g. Microsoft SQL Server, `MySQL, etc.), verify that your off-disk backup procedure includes the host database.
Changed lines 7-8 from:
* Verify that administrators (e.g. the build in [@admin@] user) can log into the interface at '''[=http://servername:9191/user=]'''
to:
* Verify that administrators (e.g. the build in [@admin@] user) can log into the interface at
-->[@http://servername:9191/user@]
Changed lines 9-10 from:
* View the about screen and ensure the expected version number is listed.
to:
* View the ''About'' screen and ensure the expected version number is listed.
Changed lines 18-19 from:
* Verify that end-users can log into the end-user web interface at '''[=http://servername:9191/user=]'''
to:
* Verify that end-users can log into the end-user web interface at '''[=http://servername:9191/user=]'''.  e.g. use a test account to verify this.
Changed lines 22-23 from:
* Perform a small manual adjustment on a user account ([@Users -> [Select User] -> Adjustment & Charges@]).  Ensure the adjustment is applied to the account balance and the user's [@Recent Transactions@] as expected.
to:
* Perform a small manual adjustment on a test user account ([@Users -> [Select User] -> Adjustment & Charges@]).  Ensure the adjustment is applied to the account balance and the user's [@Recent Transactions@] as expected.
Changed lines 35-42 from:
* Verify that you have a regular off-disk backup procedure in place and is continuing to backup as per your desired schedule.

* Do you have any external equipment, scripts, resources.  For example, scripts using the PaperCut API
.  If so, spend some time testing these external resources/services.

* If PaperCut is running on top of an external database system
(e.g. Microsoft SQL Server), verify that your off-disk backup procedure includes the host database.

* Play with any new features!  You may wish to now take some time to explore any new features.  The [[https://www.papercut.com/products/ng/release_history/ | release history]] page is a good place to start to gain a quick overview of what's new.
to:
* Verify that you have a regular off-disk backup procedure in place and is continuing to backup as per your desired schedule. [-(editors note: every year we hear horror stories about how someone thought things were backing up. Now is a good time to check!)-]

* If PaperCut is running on top of an external database system
(e.g. Microsoft SQL Server, MySQL, etc.), verify that your off-disk backup procedure includes the host database.

* Do you have any external equipment, scripts, resources?  For example, scripts using the PaperCut API?  If so, spend some time testing these external resources/services.

* Play with any new features!  You may wish
to now take some time to explore any new features.  The [[https://www.papercut.com/products/ng/release_history/ | release history]] page is a good place to start to gain a quick overview of what's new.  Also check out the [[KnownIssues|known issues]] list for any important notes associated with this release.
Added lines 37-38:
* Do you have any external equipment, scripts, resources.  For example, scripts using the PaperCut API.  If so, spend some time testing these external resources/services.
Changed lines 5-6 from:
The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.  It is advisable to print out this page (Printable View link above) an check off the steps as the tests are performed.
to:
The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.  It is advisable to print out this page (''Printable View'' link above) an check off the steps as the tests are performed.
Changed lines 3-4 from:
PaperCut is designed to support fully automated install-over-the-top upgrades.  Normally no manual upgrade tasks need to be performed, however like all server-side applications, system administrators should devote some time to testing post upgrade.  Administrators may find the following checklist useful. The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.  It is advisable to print out this page (Printable View link above) an check off the steps as the tests are performed.
to:
PaperCut is designed to support fully automated install-over-the-top upgrades.  Normally no manual upgrade tasks need to be performed, however like all server-side applications, system administrators should devote some time to testing post upgrade.  Administrators may find the following checklist useful.  The test plan may equally be applied to new installs or server migrations.

The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.  It is advisable to print out this page (Printable View link above) an check off the steps as the tests are performed.
Changed lines 3-4 from:
PaperCut is designed to support fully automated install-over-the-top upgrades.  Normally no manual upgrade tasks need to be performed, however like all server-side applications, system administrators should devote some time to testing post upgrade.  Administrators may find the following checklist useful. The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.
to:
PaperCut is designed to support fully automated install-over-the-top upgrades.  Normally no manual upgrade tasks need to be performed, however like all server-side applications, system administrators should devote some time to testing post upgrade.  Administrators may find the following checklist useful. The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.  It is advisable to print out this page (Printable View link above) an check off the steps as the tests are performed.
Changed lines 1-4 from:
(:title PaperCut NG Post Upgrade Test Plan :)

PaperCut NG is designed to support fully automated install-over-the-top upgrades.  Normally no manual upgrade tasks need to be performed, however like all server-side applications, system administrators should devote some time to testing post upgrade.  Administrators may find the following checklist useful. The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.
to:
(:title PaperCut Post Upgrade Test Plan :)

PaperCut is designed to support fully automated install-over-the-top upgrades.  Normally no manual upgrade tasks need to be performed, however like all server-side applications, system administrators should devote some time to testing post upgrade.  Administrators may find the following checklist useful. The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.
Changed lines 5-6 from:
* Verify that administrators (e.g. the build in [@admin@] user) can log into the interface at '''[@http://servername:9191/user@]'''
to:
* Verify that administrators (e.g. the build in [@admin@] user) can log into the interface at '''[=http://servername:9191/user=]'''
Changed lines 16-17 from:
* Verify that end-users can log into the end-user web interface at '''[@http://servername:9191/user@]'''
to:
* Verify that end-users can log into the end-user web interface at '''[=http://servername:9191/user=]'''
Changed lines 5-8 from:
* Verify that administrators (e.g. the build in [@admin@] user) can log into the interface at http://server_name:9191/admin

* View the about screen and ensure the last and correct version number is listed.
to:
* Verify that administrators (e.g. the build in [@admin@] user) can log into the interface at '''[@http://servername:9191/user@]'''

* View the about screen and ensure the expected version number is listed.
Changed line 13 from:
** Internet cont settings (if used)
to:
** Internet cost settings (if used)
Changed lines 16-17 from:
* Verify that end-users can log into the end-user web interface at http://servername:9191/user
to:
* Verify that end-users can log into the end-user web interface at '''[@http://servername:9191/user@]'''
Changed lines 16-17 from:
* Verify that end-users can log into the end-user web interface at http://server_name:9191/user
to:
* Verify that end-users can log into the end-user web interface at http://servername:9191/user
Added lines 37-38:
* Play with any new features!  You may wish to now take some time to explore any new features.  The [[http://papercut.biz/products/ng/release_history/ | release history]] page is a good place to start to gain a quick overview of what's new.
Added lines 1-40:
(:title PaperCut NG Post Upgrade Test Plan :)

PaperCut NG is designed to support fully automated install-over-the-top upgrades.  Normally no manual upgrade tasks need to be performed, however like all server-side applications, system administrators should devote some time to testing post upgrade.  Administrators may find the following checklist useful. The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application.

* Verify that administrators (e.g. the build in [@admin@] user) can log into the interface at http://server_name:9191/admin

* View the about screen and ensure the last and correct version number is listed.

* View general cost and system configuration settings and ensure that settings and data are still present after the upgrade:
** User accounts are listed under the Users section
** Shared Accounts listed under the Account section
** Printer cost settings (if used)
** Internet cont settings (if used)
** Historical print and log data

* Verify that end-users can log into the end-user web interface at http://server_name:9191/user

* Log into a workstation and ensure that the client starts as expected and list the current logged in userís account balance (assuming you have deployed the client).

* Perform a small manual adjustment on a user account ([@Users -> [Select User] -> Adjustment & Charges@]).  Ensure the adjustment is applied to the account balance and the user's [@Recent Transactions@] as expected.

* Print a print job under a test user account and confirm:
** Print jobs list as expected under [@Printers -> Print Log@]
** Ensure the job has charged the user as expected.
** Ensure a corresponding transaction is listed under the userís recent transactions list.

* If users (or some users) are using the '''account selection popup''' to select and charge to shared accounts, perform some printing under an appropriate user account and ensure the popup is working as expected.

* Check the '''App. Log''' (Application Event Log) section for any recent ''Warning'' or ''Error'' level messages.

* If you have any PaperCut NG extensions installed (for example, custom web layout/design, extension modules, or integration with 3rd party systems), perform some tests and ensure these are working/displaying as expected.

* Verify that you have a regular off-disk backup procedure in place and is continuing to backup as per your desired schedule.

* If PaperCut is running on top of an external database system (e.g. Microsoft SQL Server), verify that your off-disk backup procedure includes the host database.

[-keywords: testing, upgrade, update, procedure -]
----
''Categories:'' [[!Administration]], [[!Upgrading]]
----

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on July 12, 2016, at 12:51 PM
Printable View   |   Article History   |   Edit Article