The "Quality Tests" are cards defining what "Quality Checks" are going to be done and what results are expected when the "Quality Order" is created. 

Either from the "Role Center", from the "Quality Setup" ribbon or simply from searching for "Quality Tests", open the page and create a +New one. 

General FastTab

If you have a "No Series" defined, this will pre-populate the No field on the card. Manually add a number if "No Series" is setup for Manual No's. Populate the Description field (100 character limit) with the description for what the Test is for. The Version No will auto-populate to '1'. New Versions are mentioned further down on this article. 

In the Quality Team Responsible field, select from the dropdown the Team that will be responsible for the "Quality Tests". You can then assign the specific user in the Default QC Team Member field if necessary.

There is a toggle which can be edited for Blind Test. This should be 'Yes' if you want your users entering results on the "Quality Orders" without being able to see the Target Result. Leaving this as 'No' will mean the Target Result will remain visible on the "Quality Orders". 

There is also a toggle for the Signature Required option. Where this is 'Yes', a signature FastTab appears on a "Quality Order" and cannot be posted until a signature is stored against the order. Where this is 'No', this FastTab is hidden and does not require a signature prior to posting a "Quality Order". More information on how to use this process can be found on the Quality Order Card article. 

The Status will default to 'Open' but can be changed to 'Certified' or 'Closed'. 'Open' allows the Test to be editable. Changing this to 'Certified' will allow it to be used (and can then be selected on the "Test Automation" screen). Using the status of 'Closed' will signify the Test is no longer active and should not be used. 

The Tracking Code Status can be assigned and will be the status stored against the "Quality Order" and Serial No or Lot No where used prior to being posted. The Date Created field will auto-populate once the Test is created. This is pulled from the Work date. The Created By field is not editable and shows who created the "Quality Test". These are also displayed within the Factbox on the "Quality Test"as well as the list page. 

Lines FastTab

The Lines FastTab is used to store the checks that are going to be done when this Test is used along with the result parameters, i..e what are your expected results for a pass etc. 

Firstly, the Quality Check Codes can be populated manually per line, or multiple can be added at one time by using the Select Quality Checks option on the Lines FastTab ribbon which will open up a list of the "Quality Check Codes" where multiple ones can be selected and confirmed. You can have as many checks here as you wish. Once these are added, many of the other fields will auto-populate, such as the Description, Unit of Measure, Result Type and Rounding Precision which are all pulled from the "Quality Check Code" table but are all editable if required. If you want to change the order of the Quality Check Codes, you can use the Sequence option in the Lines ribbon to move the highlighted line up or down. 

The Test Iterations is used to specify the criteria that will determine the number of results per Check Code. This defaults to 'Sample Size' but other options are available to choose from such as 'Single Result' or 'Fixed No of Results'. 'Fixed No of Results' allows you to enter how many results you want to record on the "Quality Order" for the Check Code in the No of Results field. 'Single Result' will default the No of Results to blank and will require just 1 result to be input on the "Quality Order". Finally, where using 'Sample Size', this will use the sample size determined in the "Quality Automation Rules" page for the Transaction Type. This means that the No of Results do not need to be populated here. 

The Result calculation is only editable where Result Type is 'Numeric' or 'Text' but include options 'Value', 'Min', 'Max', 'Average' and 'Sum' which will look at all of the results logged on the "Quality Order" and calculate the Overall Result by this value. 

The Target Result is dependant on what Result Type is being used. The below summary confirms what can and cannot be done based on the Result Type in use. 

'Numeric': Will not use pre-defined Values from a "Quality Check Code" on "Quality Tests" so Target Result requires manual population. Allows for Result Calculation options of: 'Value', 'Min', 'Max', 'Average' & 'Sum'. Can utilise the Lower Limit/Upper Limit fields. 

'Lookup': Will allow for pre-defined fields to be selected from the Values of the "Quality Check Code" for the Target Result. Result Calculation cannot be changed from 'Value'. Lower Limit/Upper Limit fields cannot be used. 

'Text': Will not use pre-defined Values from a "Quality Check Code" on "Quality Tests" so Target Result requires manual population. Result Calculation cannot be changed from 'Value'. Lower Limit/Upper Limit fields cannot be used. 

Once your Target Result is populated with the pass rate (that is, the result you want your Check Code to achieve for the "Quality Order" to result in a 'Pass'), providing your check code has a Result Type of 'Numeric', you can utilise the Lower and Upper limit fields. 

The Lower and Upper Limit fields can be used where the result doesn't need to be a specific value but it can fall in between the lower and upper limits specified. In the example above, if my results are entered as anything from 16-20, these would all result in a 'Pass' on my "Quality Order", although if the result entered was '16', '17', '19' or '20', they would flag up as a warning on the "Quality Order". So I can still pass the order with these results but the User can see they are flagged as a warning where they are within my limit criteria.

Where you are only wanting the "Quality Order" to pass if these are met (or the Target Result is achieved if Lower and Upper Limits are not in use), leave the Optional field as 'No'. Where this is 'Yes', the "Quality Order" will not log as a fail if a result is entered outside of these parameters. It also means that where Optional is 'Yes', the Quality Check Code does not need to be completed on the "Quality Order". 

In the header of the Lines FastTab, you can some other options. For Quality Check Codes that are Result Type 'Lookup', you can view the stored values here within the Lookup Values option. Alternatively, highlight a line in the Lines FastTab and click onto Instructions to see if there are any Instructions stored. These are pulled directly from the "Check Codes" and are also visible on the "Quality Orders". Selecting New Line will add a new line above the highlighted line and selecting Delete Line will delete the highlighted line from the Lines table. 

Once all data is populated, ensure the Status is changed to 'Certified'. 


If you wish to make a change to a "Quality Test" but do not want to override the test itself, you can Create New Version either from the "Quality Tests" list page ribbon or card itself. If doing this from the list page, highlight the Test you want to make a new version for and press the Create New Version button in the ribbon. Choosing this option will immediately change the status of the original version to 'Closed' and will create a new Quality Test using the same data as the one previous, leaving the status as 'Open', allowing you to make your changes before certifying the test. The Version No will be updated to show the next available number in the sequence.

You can also view all versions of the Test by selecting the Versions button in the ribbon from both the "Quality Tests" list page and card. This will show all version history for the Test. There is also a Factbox available from both the "Quality Tests" list and card pages which will show the Version Numbers, Status, Date Created and what User it was Created By

Finally, as an additional useful tool, from both the "Quality Tests" list and card pages, you can use the Where Used option which will open up a filtered view of the "Quality Automation rules" page where that Test No is used.