A WATS Client converter plugin for importing import files produced by ATML test tools to WATS.
This repository is the same as the ATMLImporter converter built-in to the WATS Client. The source code is provided so you may create your own version based on it, to add support for custom properties or other extensions.
This converter uses the following parameters:
| Parameter | Default value | Description |
|---|---|---|
| partNumber | NA | If log is missing a part number, use this one. |
| partRevision | 10 | If log is missing a revision, use this one. |
| operationTypeCode | 10 | If log is missing operation code (process code), use this one. |
| operator | oper | If log is missing sequence name, use this one. |
| sequenceVersion | 0.0.0 | If log is missing sequence version, use this one. |
The project uses the MSTest framework for testing the converter.
It is setup with two tests; one for setting up the API by registering the client to your WATS, and one for running the converter.
The values are hardcoded in the test, so you will need to change the values to reflect your setup.
- In SetupClient, fill in your information in the the call to RegisterClient.
- In TestConverter, fill in the path to the file you want to test the converter with. There are example files in the Examples folder.
- Run SetupClient once, then you can run TestConverter as many times as you want.
We're open to suggestions! Feel free open an issue or create a pull request.
Please read Contributing for details on contributions.
Symptom:
- Converter did not start after being configured.
Possible cause:
- WATS Client Service does not have folder permission to the input path.
- WATS Client Service was not restarted after configuration.
Possible solution:
- Give NETWORK SERVICE write permission to the input path folder
- Make a change in a converter configuration and undo the change, click APPLY. When asked to restart the service, click Yes.
Symptom:
- The converter class drop down list in the Client configurator is empty after adding a converter DLL.
Possible cause:
- The DLL file is blocked. Windows blocks files that it thinks are untrusted, which stops them from being executed.
Possible solution:
- Open properties on the file and unblock it.
Contact Virinco support, and include the wats.log file: Where to find the wats log file at the Client.
- Issues with the converter or suggestions for improvements can be submitted as an issue here on GitHub.
- Ask questions about WATS in the WATS Community Help
- Suggestions for the WATS Client itself or WATS in general can be submitted to the WATS Idea Exchange
- Sensitive installation issues or other sensitive questions can be sent to support@virinco.com
This project is licensed under the LGPLv3 which is an extention of the GPLv3.