mirror of
https://github.com/inventree/InvenTree.git
synced 2025-04-30 12:36:45 +00:00
3880e6f07f
* Add "testable" field to the Part model - Default = False - Determines whether a particular part can have tests defined against it * Adds data migration to set default 'testable' state * Update part serializers * CUI: Update table filters * PUI: Update tables and filters * CUI: Update part detail page * PUI: Update part detail page * Update CUI * Update build pages * Update BuildLine serializer * Bump API version * Update docs * Add 'testable' to fieldset
51 lines
2.3 KiB
Markdown
51 lines
2.3 KiB
Markdown
---
|
|
title: Stock Test Result
|
|
---
|
|
|
|
## Stock Test Result
|
|
|
|
Stock items which are associated with a [testable part](../part/part.md#testable) 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](../part/test.md), against which test data can be uploaded. Additionally, arbitrary test information can be assigned to the stock item.
|
|
|
|
{% with id="stock_test_results", url="stock/test_results.png", description="Stock Item Test Results" %}
|
|
{% include 'img.html' %}
|
|
{% endwith %}
|
|
|
|
### Test Result Fields
|
|
|
|
#### Test Template
|
|
|
|
The *template* field links to a [Part Test Template](../part/test.md#part-test-templates) 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](../report/report.md) 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](../api/api.md) or the [InvenTree Python Interface](../api/python/python.md).
|
|
|
|
!!! 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.
|