Troubleshooting

No 'Interface Definition' and 'Coverage Definition' tab is shown for a selected ATGConfiguration.

ATG data are related to model elements in a test architecture. If test achitecture is in an unclean state after 'Update TestCase', 'Update TestContext', or 'Update TestPackage', ATG refuses to access the test architecture data. Try 'Clean TestPackage' and then select the ATG Configuration again.

No 'Interface Definition' tab is shown for a selected ATGComponent.

ATG data are related to model elements in a test architecture. If test achitecture is an unclean status after 'Update TestCase', 'Update TestContext', or 'Update TestPackage', ATG refuses to access the test architecture data. Try 'Clean TestPackage' and then select the ATG Component again.

A class is greyed out in the input interface dialog and no instance can be specified

Most probably the class has either no operations or receptions at all or has only operations with unsupported argument types.

If the respective class is instantiated as SUT in the test architecture, consider implementing appropriate relay operations in test compomnents that are connected to the SUT.

A class is greyed out in the traced instances and messages interface dialog and no instance can be specified

Most probably, the class has either no operations or receptions at all or has only operations and receptions with unsupported argument types.

If the class has no operations or receptions, then there is nothing to be recorded in the test cases and it makes no sense to select the class in the traced instances and messages interface.

If operation calls and receptions shall be traced regardless of their actual argument values, property AutomaticTestGenerator::Settings::DisableTypeApplicabilityCheckInTracedMessages of the code generation configuration to which the ATGComponent or ATGConfiguration refers can be checked. In this case, the respective operation calls and event receptions will be recorded with '*' (don't care) as arguments.

An operation or event reception is greyed out and can't be selected in the input interface dialog

The operation or event most probably has arguments of unsupported types, such as reference arguments or pointers to structs, e.t.c.

E.g. for enums, the default input usage in Rhapsody is const $type& (property CPP_CG.Type.In of the type declaration). Since ATG doesn't support reference types as operation arguments in the input interface, the issue can be solved in two different ways:

1. If the respective class is instantiated as SUT in the test architecture, consider implementing appropriate relay operations in test compomnents that are connected to the SUT.
2. Property CPP_CG.Type.In of the respective type declaration can be modified, s.t. ATG can support the argument type.

An operation or event reception is greyed out and can't be selected in the traced instances and messages interface dialog

If operation calls and receptions shall be traced regardless of their actual argument values, property AutomaticTestGenerator::Settings::DisableTypeApplicabilityCheckInTracedMessages of the code generation configuration to which the ATGComponent or ATGConfiguration refers can be checked. In this case, the respective operation calls and event receptions will be recorded with '*' (don't care) as arguments.

I can't find a particular class in the interface dialog

ATG per default keeps the set of offered classes in the interface dialog as small as possible. Only classes are offered which are instantiated in the test context as either SUT or test component instance. If this filtering is too strong, the filter can be deactivated using property AutomaticTestGenerator::Settings::StimulationInterfaceFilterMode of the code generation configuration to which the ATGComponent or ATGConfiguration refers. If set to None, no filtering will be applied. The effect of modifying this property will take place upon 'Synchronize ATG Data with Application'

Exported test cases fail due to time intervals in the TestScenarios

ATG can only record timeouts at the instant of time they are appearing in the application during test case generation. In particular, ATG has no knowledge about the instant of time at which the timeouts were scheduled or maybe canceled and possibly re-scheduled. Therefore, ATG adds a time intervall with the expired timeout duration to the test context instance line at the point in time at which the timeout was observed. This works pretty well with simulated time model in almost all cases, but maybe a too coarse abstraction in particular in combination with real time code generation setting.

If exported test cases fail due to time intervals, only manual corrections will solve the problem.

I can't generate test cases because ATG complains about missing files

Consider adding the missing files manually to the ATGConfiguration.

ATG does not cover all model elements or doesn't generate test cases at all

• Check that your application contains Initial Instances.
• try more run time…
• if the model contains time triggered transition with large timeout values: try modifying timestep value appropriately
• try beam search
• check that the Input Interface has been defined appropriately
• check that the argument ranges of selected messages in the Provided Interface are set correctly
• check if unreachable test goals might be dead model parts…

Not all messages of interest appear in the generated test cases

• check whether all pre-conditions of the message are fulfilled
• check that the Traced Instances and Messages interface has been defined appropriately