Re: [Rails-devel] Automated testing for Rails

[Stefan F. <ste...@we...>]

Erik:
- Reversing the tree makes sense. 

- For faked games there is the category test_cases.
For testing reasons it does not matter if revenues are faked, as long as the 
game runs through. I did the same: Testing game end is easy if you have one 
company pay out $20.000 in OR 2.

In any case it makes sense that you add your test save files yourself to the 
tree. 

And I promise that I will never trust any of your save files...

Stefan

On Tuesday 23 March 2010 21:18:21 Erik Vos wrote:
> Looks very good to me.
>
> I generally agree with your proposals. Just one remark: can't the tree
> hierarchy be better reversed?
> For what it's worth: I would tend to select a game first, then look what
> saved files/test cases exist for that game.
>
> And a warning: most of the saved files I have sent you off-list do NOT
> constitute valid games.
> The revenues have often been faked, either to construct a particular test
> case, or just because I was lazy.
> Never trust my saved files!
>
> Erik.
>
> -----Original Message-----
> From: Stefan Frey [mailto:ste...@we...]
> Sent: Tuesday 23 March 2010 19:53
> To: Development list for Rails: an 18xx game
> Subject: [Rails-devel] Automated testing for Rails
>
> I have added automated regression testing for Rails in CVS.
>
> How does it work:
> * For a set of Rails save files (which are known that they are correct)
> game
>
> reports are created and stored alongside with the save files.
> Then each time the tests are run, each game is replayed by Rails on the new
> code base and the game reports are compared to the stored ones.
>
> * Anytime a difference in the game reports occurs, this test reports the
> error
> and displays the first line, where the game reports deviate.
>
> More instructions and comments for developers see attached text file. In
> addition I have added an example report of a current test run.
>
> Stefan
>
> I have not uploaded my preliminary test suite so far, as I want to ask for
> opinion on the tree structure first.
>
> My proposal is:
>
> Convention for file names:
> {18xx}_{noMap - if used}_{author}_{nb of players}_{end round}_{end
> condition}_{special remarks}
>
> -> Bug reports
> The game name should include the bug number if possible.
> below that with categories, that still have to be defined.
>
> -> Finished games
> real plays
> below that with one folder for each 18xx
>
> -> Pbem games
> currently running pbem games
> below that with one folder for each 18xx
>
> -> Test cases
> hand crafted settings for specific testing
> below that with one folder for each 18xx
>
> -> Test games
> simulated games
> below that with one folder for each 18xx
>
>
>
> ---------------------------------------------------------------------------
>--- Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel