Logo etsi

ETSI's Bug Tracker

Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0005039ETSI TTCN-3 Quality CheckerT3Q toolpublic01-04-2009 15:4029-11-2010 09:03
ReporterWolfgang Seka 
Assigned ToPhilip Makedonski 
PrioritynormalSeverityfeatureReproducibilityhave not tried
StatusfeedbackResolutionreopened 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0005039: additional checks on templates
Description1. messageTemplateWithWildcardsRegExp
those templates shall be used in recceive statements only;
they may have any kind of parameter (where as messageTemplate shall follow restrictions as below)

2. messageTemplate
- shall be "template (value)"
- shall not have parameters being "template" or "template (present)"
  (i.e. parameters shall be values, "template (omit)" or "template (value)"

example:
template (value) MyType cs_MyType(
                     integer p_Int, // allowed
                     template (value) MySubType1 p_SubType1, // allowed
                     template (omit) MySubType2 p_SubType2, // allowed
                     template (present) MySubType3 p_SubType3, // not allowed
                     template MySubType4 p_SubType4) // not allowed
{
 ...
}
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0008695)
Philip Makedonski (developer)
01-06-2009 09:49

Templates with wildcards do not necessarily need to have matching expressions, so it should be checked if it is a template or a template with matching expression, and if it is one with a matching expression, then it should be restricted to the "mw_" prefix, otherwise it may either start with "m_" or "mw_".
(0008714)
user257
02-06-2009 12:50

1. the tool check the CONTENT of the template
2. if there's any wildcard then it's a receiving template and the corresponding naming conventions should apply ("mw_" by default)
3. if there's no wildcard then it's a sending or receiving template and the corresponding naming convention should apply ("m_" by default)
3b. If you want to use a template without wildcards for receiving purposes then you have to change the default "m_" to "m_ and mw_"
(0009816)
Miguel Angel Reina Ortega (reporter)
29-11-2010 09:03

We'd like to suggest a different checking logic. Right now, we have:

- Checking content -> naming conventions should apply accordingly -> it's either sending or receiving template in accordance with the content.

This leads to manipulate the configuration file in order to allow to have mw_ templates without wildcards, of course, for receiving purposes.

The checking logic we suggest is as follows:

- Check template name -> Check the content -> Check the purpose (sending or receiving)

so we obtain the following scheme:

- m_ -> check that there's no wildcard -> check that it is used for sending purposes

- mw_ -> no check needed, it may contain wildcards -> check that it is used for receiving purposes

With this logic, there is no need of manipulating the configuration file.

- Issue History
Date Modified Username Field Change
01-04-2009 15:40 Wolfgang Seka New Issue
01-04-2009 15:40 Wolfgang Seka Status new => assigned
01-04-2009 15:40 Wolfgang Seka Assigned To => Jens Grabowski
03-04-2009 12:32 Philip Makedonski Assigned To Jens Grabowski => Philip Makedonski
01-06-2009 09:49 Philip Makedonski Note Added: 0008695
02-06-2009 11:49 user257 Note Added: 0008712
02-06-2009 12:50 user257 Note Added: 0008714
02-06-2009 12:50 user257 Note Deleted: 0008712
26-11-2009 14:20 Philip Makedonski Status assigned => resolved
26-11-2009 14:20 Philip Makedonski Resolution open => fixed
29-11-2010 08:11 Sebastian Muellers Status resolved => feedback
29-11-2010 08:11 Sebastian Muellers Resolution fixed => reopened
29-11-2010 09:03 Miguel Angel Reina Ortega Note Added: 0009816


MantisBT 1.2.14 [^]
Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker