ride won't save new-but-mostly-empty suite

[yanne]

Originally submitted to Google Code by bryan.oakley on 31 Mar 2009

ride 0.13.1

If I create a new project of type directory, create a new suite under that
and then click save I get a dialog that says "no modifications since last
save".

If I now exit ride, nothing exists on disk. It refused to save when I
asked, and then refused to automatically save. My work, little that there
was, is lost.

I don't quite understand why it would refuse to save when I ask it to, but
at the very least if it's going to refuse to save it should do so only if
there is already something on disk.

From a usability point of view, it's much more usable if it just does what
I ask, or if it's absolutely certain that saving is redundant it should
just silently do nothing (though what's the harm in saving?)

[yanne]

Originally submitted to Google Code by @yanne on 27 Apr 2009

There are actually two separate issues here.

1. The notification of no changes, this could easily be removed.

2. Serialization of empty suite. Currently, RIDE does not save an empty test suite,
   because a file with empty or non-existing test case table cannot be read from disk.
   This is due to limitation in Robot Framework test data parsing, which RIDE internally
   uses to process the test data. So in order to save a file suite to disk, it must have
   at least one test case. If user tries to save a suite with no tests, there should
   probably be some kind of warning given.

[yanne]

Originally submitted to Google Code by @yanne on 27 Apr 2009

Removed warning for no changes and added warning that suites with no tests are not
properly serialized in r315.