11ab0203b1
* Add builtin plugin for auto-issuing orders * Add plugin to auto-issue orders * Add placeholder documentation * Fix typo * Adds image macro - To replace img.html - includes checking if file exists * Fix tooltips * More docs * Adjust plugin settings filters * docs * More docs * More docs * Updates * Less restrictive URL checking * Refactor build order page * Fix typo * Allow 429 * Debug output * More debug * Construct assets dir * Cleanup * Update docs README * Refactoring more pages * Fix image link * Fix SSO settings * Add hook to check for missing settings - Ensure that all settings are documented! * Add missing user settings * Update docstring * Tweak SSO.md * Image updates * More updates * Tweaks * Exclude orders without a target_date * Fix for issuing build orders * Further refactoring * Fixes * Image refactoring * More refactoring * More refactoring * Refactor app images * Fix pathing issues * Suppress some openapidocs warnings in logs (much easier to debug docs build issues) * Fix image reference * Reduce error messages * Fix image links * Fix image links * Reduce docs log output * Ensure settings are loaded before displaying them * Fix for UI test * Fix unit test * Test tweaks
2.2 KiB
title
| title |
|---|
| Stock Test Result |
Stock Test Result
Stock items which are associated with a testable part can have associated test data - this is particularly useful for tracking unit testing / commissioning / acceptance data against a serialized stock item.
The master "Part" record for the stock item can define multiple test templates, against which test data can be uploaded. Additionally, arbitrary test information can be assigned to the stock item.
{{ image("stock/test_results.png", title="Stock Item Test Results") }}
Test Result Fields
Test Template
The template field links to a Part Test Template object. Each test result instance must link to a test template.
Result
Boolean pass/fail status of the test.
Value
Optional value uploaded as part of the test data. For example if the test is to record the firmware version of a programmed device, the version number can be added here.
Notes
Optional field available for extra notes.
Attachment
A given test result may require an attached file which contains extra test information.
Multiple Test Results
Multiple results can be uploaded against the same test name. In cases where multiple test results are uploaded, the most recent value is used to determine the pass/fail status of the test. It is useful to keep all test records as a given test might be required to run multiple times, if (for example) it fails the first time and then something must be fixed before running the test again.
Reporting
For any information regarding the reporting architecture, please refer to the Report Generation page.
Automated Test Integration
The stock item testing framework is especially useful when integrating with an automated acceptance testing framework. Test results can be uploaded using the InvenTree API or the InvenTree Python Interface.
!!! info "Example" You design and sell a temperature sensor which needs to be calibrated before it can be sold. An automated calibration tool sets the offset in the device, and uploads a test result to the InvenTree database.