Closed GoogleCodeExporter closed 9 years ago
Just a bug to point out about that would effect this. Some video plugins (I've
only
seem this in Rice personally) don't properly set up the full video state on
resume
from a snapshot.
To see this yourself:
1) Load Mario64.
2) Play until you get to Level 1, then pause and see the level status / quit
text.
3) Save a snapshot.
4) End emulation, reload Mario64.
5) Load snapshot immediately after seeing Mario64 text - the level status /
quit
text will not appear.
6) End emulation, reload Mario64.
7) Load snapshot after getting to the select saved game text - the level status
/
quit text will appear.
I'm assuming that the automated tested would load a ROM and a savestate.
Original comment by sknau...@wesleyan.edu
on 19 Apr 2008 at 5:47
I'm not planning on doing automatic savestate loading for the initial setup.
Taking
shots from the intro and demo should suffice, since the demos and the actual
game use
the same engine and would be susceptible to the same bugs. It is possible to
add
automatic savestate loading at a later date to test specific problems if
necessary,
but right now I'd rather spend the extra time working on other fixes and
features.
Original comment by richard...@gmail.com
on 19 Apr 2008 at 6:26
Just certain bugs don't show up in the intro / demos. The biggest I can think
off
the top of my head is Link's 2D preview in the pause menu.
It's okay if the first version of automated testing doesn't get these. Sadly
after
using mupen with a wider number of ROMs, I see there are some more major
graphcs
bugs to deal with first.
Original comment by sknau...@wesleyan.edu
on 19 Apr 2008 at 7:39
What would this be written in? C?
Original comment by sgorman07@gmail.com
on 19 Apr 2008 at 10:41
Since it's mostly going to involve text processing and shell calls, I'll write
the
regression test controller in Python.
Original comment by richard...@gmail.com
on 20 Apr 2008 at 12:22
Heh. While I have no experience with emulation and almost none with C, I do
like
Mupen64Plus and I'm fairly good with Python. Maybe I'll make some time to help
out
during my summer vacation.
Original comment by stephan....@gmail.com
on 22 Apr 2008 at 3:35
My screenshot modification should help you out in this case, this will allow you
categorize the screenshots easier for review.
Original comment by sgorman07@gmail.com
on 23 Apr 2008 at 8:34
The nightly auto-regression is up and running as of April 28; the script code
and
initial configuration file were committed in rev 324. There are 658
screenshots from
36 games taken and compared against reference images. A test report including
build
warnings/errors and any differences between test and reference images is
emailed to
developers, and the images and report are archived on my local PC.
Original comment by richard...@gmail.com
on 28 Apr 2008 at 2:14
Original issue reported on code.google.com by
richard...@gmail.com
on 19 Apr 2008 at 4:29