The current test script for the plugin included samples for
- Material
- Read one material by the keys
- Read all materials
- Create new material with string properties
- Update existing material with description (string property)
- Bom
- Read one Bom by the keys and expand bomRows
- Create new BOM with one bomrow
- Documents
- Create new Document with metadata and upload binary file
- Read Document by the keys
- Download Document binary by the keys
Extend with tests
In the projects we tackle often some issues when new versions of the ERP API is released.
In order to verify fast that the old functionality still works it helps dramatically to execute automatic tests without depending on Inventor/Vault workflows.
You can find a very good example of Pester tests that are ready to execute and test all the ERP API functionality that we require during a standard project here..
This includes also:
- Read materials with filter
- Add to existing boms a new row
- Remove from existing boms an existing row
- Adding same bom again -> test error handling
- Update bom header
- Update bom row
- Reporting of the performance of API calls to ensure that we know when the API gets slower, in this way can communicate to the customer that it does not depend on our side but on the ERP side.
- Here are missing documents tests
- The goal of the new test script is to test all AP functionality what we require on the client-side
The current test script for the plugin included samples for
Extend with tests
In the projects we tackle often some issues when new versions of the ERP API is released.
In order to verify fast that the old functionality still works it helps dramatically to execute automatic tests without depending on Inventor/Vault workflows.
You can find a very good example of Pester tests that are ready to execute and test all the ERP API functionality that we require during a standard project here..
This includes also: