Hi folks,

Let me summarize the yesterday's discussion in a few keys points:

Greg's proposal aims at simplicity and is useful mainly for test cases which can be written in a few minutes. More complex test cases are not suitable for the YAML approach.
The above implies that the YAML based test cases would be supported alongside the existing approach. This fast way to implement simple test cases would likely be a valuable addition.
The big picture idea behind the YAML test cases is to take an application with interactive input, send commands, collect output and compare the output with expected string(s).
Greg may be able to make the code available and may assess how to integrate it with DTS.

Regards,

Juraj

On Mon, Jan 8, 2024 at 6:36 PM Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com> wrote:

<snip>

>
> Hello Honnappa,
>
> [snip]
>
> > Hi Gregory,
> > I do not fully understand your proposal, it will be helpful to join the DTS
> meetings to discuss this further.
> >
>
> Agree, let's discuss the proposal details during the DTS meeting.
>
> > YAML has wide support built around it. By using our own text format, we will
> have to build the parsing support etc ourselves.
> >
> > However, YAML is supposed to be easy to read and understand. Is it just a
> matter for getting used to it?
> >
>
> I selected YAML for 2 reasons:
> * Plain and intuitive YAML format minimized test meta data.
> By the meta data I refer to control tags and markup characters
> that are not test commands.
> * YAML has Python parser.
I have mis-understood your proposal. I agree with your above comments.
+1 for the proposal.

>
> Regards,
> Gregory
>
>