Closed GoogleCodeExporter closed 9 years ago
Some issues (priorities A-C):
- Mapping on the trace validator side should be done based on the DLT context
id, not the Franca file path. (A)
- In the DLT viewer plug-in's "available context list", color according to the
status of the trace validation (if at least one trace message is read, the
context id should be red). (A)
- All trace messages which do not have the format ([call|respond|signal]_.*)
shall be ignored in the trace viewer plugin. If a context doesn't contain any
message with this format, it should not be listed in the "available contexts"
(A)
- After one message has been marked red, the trace validator should start over.
(B)
- If the user selects another fidl file in the DLT viewer, the validation
should start over for all messages in the "trace of context" list (this needs a
change both in the viewer plug-in and in the OSGI part). (B)
- Performance optimization: Collect several messages (with a timeout) before
sending them to the trace validator. (C)
- The trace validator (OSGI) server should be started by the DLT viewer
plug-in, if it is not already running. (C)
Original comment by klaus.birken@gmail.com
on 27 Sep 2013 at 8:56
Some more issues after testing a bit:
- Selecting one trace element in the plug-in's "Messages" list should select
the corresponding message in DLT viewer's original trace message view (useful
for locating a "red" trace message in the complete stream of trace messages) (B)
- DLT viewer has a toggle in the toolbar button "Scroll automatically to the
end of log when receiving data". This toggle should affect also the behavior of
the plug-ins's "Messages" list (for the currently selected context) (C)
Original comment by klaus.birken@gmail.com
on 27 Sep 2013 at 8:28
The DLT viewer plug-in should be renamed to "Contract Validator" (currently
"Trace viewer", but this could also refer to any kind of DLT plug-in, even DLT
viewer itself). It is sufficient to do the renaming in the DLT UI first (and
not in source packages, classes, repos... - this can be done later).
Original comment by klaus.birken@gmail.com
on 30 Sep 2013 at 11:31
- mapping OK
- context coloring OK
- message filtering OK
Original comment by szabt...@gmail.com
on 30 Sep 2013 at 11:35
The related C/C++ source codes can be found here:
https://github.com/szabta89/Franca-DLT
Original comment by szabt...@gmail.com
on 30 Sep 2013 at 11:36
- renaming OK
Original comment by szabt...@gmail.com
on 30 Sep 2013 at 1:35
- new file selection triggers revalidation OK
Original comment by szabt...@gmail.com
on 1 Oct 2013 at 12:58
- the trace validator is able to recover after an error OK (proper expectations
are printed as tooltip messages)
Original comment by szabt...@gmail.com
on 2 Oct 2013 at 1:56
This implementation is based on the Franca tracevalidator plug-in, which is
part of the release of Franca 0.9.0 and later (see issue 25 for details).
Original comment by klaus.birken@gmail.com
on 7 May 2014 at 4:22
Original comment by klaus.birken@gmail.com
on 25 Jan 2015 at 12:29
Original issue reported on code.google.com by
klaus.birken@gmail.com
on 27 Sep 2013 at 8:28