printIQ Initial & Smoke Testing Releases
As part of our ongoing steps to ensure stability in every patch release we do and to ensure a successful roll out of every patch release and upgrade that is carried out on your printIQ site we follow a number of checks before and after this process.
Prior to any release being carried out we will perform initial testing on your site, this comprises of essentially duplicating your database and doing an offline run of the upgrade to ensure all scripts run successfully and without error. Only if these are successful will an release perform. Should there be an error our Development Team will check the issue and perform the relevant fix to ensure the upgrade goes without hitch.
Post release we will perform smoke testing on your printIQ site. This comprises of running a test job from start to finish as well as checking all job boards, all menus, markup templates and APIs. We will setup a test estimate on with a user called PrintIQ.Auto.Test and this will be used to replicate a user creating an estimate, pushing this into a job, uploading artwork and carrying out all steps up until the point of dispatch and invoicing.
For this process we will normally use a test customer within printIQ to carry out this testing. So we ask that TestCustomer (or similar accounts) are not deactivated within printIQ and do not have any manual overrides such as Approvals enabled. Should a smoke test fail a member of the printIQ team will log into the site to investigate the fault. Should it be the user account is in-active then the standard process would be to activate this customer account and check the test estimate works.
Any Jobs and Proofs created during this process will be removed once the test has been completed. No invoices will be created on a live site. At times depending on when the release was carried out, these tests may be running during the time users are logged into the system. So if you see a test job appear, do not worry as it will be removed after.
This smoke tests evolve as the version evolve to catch as many feature changes and updates as possible. We try to make sure smoke testing will only kick in during non business hours but there can be occasion that they will run during, they are non intrusive and a clean up is always performed after.
Related Articles
User Positions
User Positions, Roles and Details Setup & Admin This article describes the tools available for managing user accesses. It covers User Positions, User Details and User Roles. There are three user types – Staff, Customer and Supplier: Customer users ...Automated order creation – DirectoryMonitor2 Setup
Introduction The DirectoryMonitor2 ( app) is an add-on module to automate order creation within printIQ. The app is designed to monitor folders (based on configuration), and initiate processing based on files found in the folders. The application ...XERO - Back End Settings in printIQ
Invoice status passing to Xero When invoices are exported from printIQ, these setting’s control the status of sales and supplier invoices imported into Xero. Yes, the invoices will import into Xero under ‘Draft’ status. No, the invoices will import ...Xero Integration - Workflow and FAQ
Workflow Workflow tends to vary from business to business depending on how you prefer to operate. Generally, printIQ and Xero will interact as follows: Customers / debtors Sales invoices are generated and emailed out of printIQ. Data from each ...Setup - Operations in printIQ
printIQ implementation strategy Planning your operations and structure Introduction: What is an operation? Within printIQ, we have a concept of an operation which is a task that is completed on a job. One or more operations are then completed in ...