From OpenTTCN DocZone
Last modified February 18, 2008
How to submit an issue report
Before you submit an issue to support@openttcn.fi, please make sure you have included the following information to your issue report. This helps us serve your support request faster and makes our response more accurate.
Background information
- operating system in use
- Tester and SDK version in use
- do you use dual core multiprocessor system or not
- how much physical memory your hardware has
If you include an excerpt from a test log
- make sure you run your test campaign using "tester run -f -l -b -e -m MySession MyTroubledTestcase" set of command-line options before submitting an issue; it is important that issue report containing test log is generated using the aforementioned set of options
- include the full content of the line that produces test case error, together with full reason of an error, file name and line number; simply saying that a test case produces an error is not enough
- include stack trace related to the test case error if available
If your problem is adapter-related
- make sure you have enabled adapter debug printout; in ANSI C SDK this is done through the following statement in the main() function:
otSetSAFlags(OT_SA_FLAG_VERBOSE);
- attach adapter debug output related to the issue together with the issue report
- make sure you have value validation enabled (it is enabled by default); in ANSI C SDK this is done through the following statement in the main() function:
otSetCDFlags(OT_CD_FLAG_VALIDATE_DECODED_VALUE);
Other things to consider
We do not generally serve requests caused by errors or non-conformant definitions in test suites, or related to TTCN-3, C, Java, or C# programming practices in general, unless you have purchased consulting or support contract that explicitly includes support for such requests. Such questions shall be otherwise asked directly in a forum dedicated to the language or test suite in question.