Re: [RFC] Merge mi-cli.exp and mi2-cli.exp

[Yao Qi <yao at codesourcery dot com>]

On 09/03/2012 05:08 PM, Vladimir Prus wrote:
> Yep, that was the intent -- with the extra twist that tests for MI and
> MI2 are not necessary
> identical. In other words, MI2 tests are tests for MI2 when MI2 was
> declared "done", and the
> idea was that the output with "-i=mi2" would remain the same for years.
> -i=mi is our current
> version of MI, which may evolve, and when MI3 is declared "done", the
> current tests will
> be copied to mi3-* tests to keep backward compatibility in future.

mi and mi2 test cases are not necessarily identical, but most of them 
should be the same, and the difference should be a small part in test. 
I can't see the benefit of simply copying mi tests to mi2 tests.

We can claim that a certain version of MI is done, but I am not sure we 
can claim the testing to a certain version or some versions of MI is 
done, unless we have a confident coverage result.  What should we do if 
we want to add more tests to all existing MI?  The tests are not 
specific to a certain version of MI.  Do we have to copy the new tests 
to mi-foo.exp and mi2-foo.exp?

I am writing some tests on breakpoint-modified notification on all types 
of 'breakpoint', such as watchpoint, catchpoint, dprintf, tracepoint, 
etc.  I write them in mi-cli.exp, but I am wondering whether I should 
add them to mi2-cli.exp as well.

--
Yao