Difference between revisions of "Release Testing"

From ScummVM :: Wiki
Jump to navigation Jump to search
m (end of release testing)
(→‎Release Testing for ScummVM: add link for 2.0.0 testing)
 
(31 intermediate revisions by 7 users not shown)
Line 1: Line 1:
== Release Testing for ScummVM==
+
== Release Testing for ScummVM ==
  
 +
* [[Release Testing/2.0.0|2.0.0]]
 +
* [[Release Testing/1.9.0|1.9.0]]
 +
* [[Release Testing/1.8.1|1.8.1]]
 +
* [[Release Testing/1.8.0|1.8.0]]
 +
* [[Release Testing/1.7.0|1.7.0]]
 +
* [[Release Testing/1.6.0|1.6.0]]
 +
* [[Release Testing/1.5.0|1.5.0]]
 +
* [[Release Testing/1.4.0|1.4.0]]
 +
* [[Release Testing/1.3.0|1.3.0]]
 +
* [[Release Testing/1.2.0|1.2.0]]/[[SCI/Testing|SCI]]
 +
* [[Release Testing/1.1.0|1.1.0]]
 +
* [[Release Testing/1.0.0|1.0.0]]
 +
* [[Release Testing/0.13.0|0.13.0]]
 +
* [[Release Testing/0.12.0|0.12.0]]
 +
* [[Release Testing/0.11.0|0.11.0]]
 +
* [[Release Testing/0.10.0|0.10.0]]
 +
* [[Release Testing/0.9.0|0.9.0]]
 
* [[Release Testing/0.8.0|0.8.0]]
 
* [[Release Testing/0.8.0|0.8.0]]
* [[Release Testing/0.9.0|0.9.0]]
 
* [[Release Testing/0.10.0|0.10.0]]
 
* [[Release Testing/0.11.0|0.11.0]]
 
* [[Release Testing/0.12.0|0.12.0]]
 
  
 
== Testing Guidelines ==
 
== Testing Guidelines ==
  
* Use the latest SVN build which you may find at the bottom of our [http://www.scummvm.org/downloads.php download page].
+
* Use the latest build which you may find at the bottom of our [http://scummvm.org/downloads/ download page]. After we branched please use the latest '''stable''' builds when downloading from our [http://buildbot.scummvm.org/builds.html Buildbot].
 
* Use the launcher to add your game and see if it was detected normally, even if you already have this game already added. Start newly added target.
 
* Use the launcher to add your game and see if it was detected normally, even if you already have this game already added. Start newly added target.
* Preferably test detection of every game/demo you have, even when you're not going to play them
+
* Preferably test detection of every game/demo you have, even when you're not going to play them.
* Play game from beginning through the end
+
* Play game from beginning through the end.
* Preferably use of save/load facility
+
* Preferably use of save/load facility.
 
* '''Do not''' skip cutscenes.
 
* '''Do not''' skip cutscenes.
* If you encounter any problems, please, submit a bug report at our [http://sourceforge.net/tracker/?atid=418820&group_id=37116&func=browse Bugtracker]
+
* If you encounter any problems, please, submit a bug report at our [https://bugs.scummvm.org/ bug tracker].
* If a game has several branches, test as many variants as you can
+
* If a game has several branches, test as many variants as you can.
 
* At least 1 user should test each game, preferably but not obligatory on different platforms.
 
* At least 1 user should test each game, preferably but not obligatory on different platforms.
** However, more than one users should test games that satisfy one or more of the following conditions:
+
** However, more than one user should test games that satisfy one or more of the following conditions:
*** It is a multiple path game (such as ''Fate of Atlantis'' or ''Maniac Mansion'')
+
*** It is a multiple path game (such as ''Fate of Atlantis'' or ''Maniac Mansion''). We designate such games with a '''''#''''' (hash symbol).
*** It is a new game for this release
+
*** It is a new game for this release. We designate such games with a '''''*''''' (star symbol).
*** We designate such games with a '''''#''''' (hash symbol)
 
  
 
== What to provide when you encounter a bug ==
 
== What to provide when you encounter a bug ==
  
Please provide information on our bug tracker. Please, do not post bugs to our forums as that makes discussions and bug fixing progress tracking practically impossible
+
Please provide information on our bug tracker. Please, do not post bugs to our forums as that makes discussions and bug fixing progress tracking practically impossible.
  
* Make sure that you have a working mail set up at your sf.net account. In this case you will receive our reply to your bug report
+
* Make sure that you have a working mail set up at your GitHub account. In this case you will receive our reply to your bug report.
* Snapshot date (but please, always test with latest one)
+
* Snapshot date (but please, always test with the latest one).
* Bug details, including instructions on reproducing it
+
* Bug details, including instructions on reproducing it.
 
* Language of game (English, German...).  
 
* Language of game (English, German...).  
* Is it fan translation or not.
+
* If it is a fan translation, mention it.
* Version of game (talkie, floppy...)
+
* Version of game (talkie, floppy...).
* Whether sound was compressed or not
+
* Whether the sound was compressed or not.
* Platform and compiler (Linux, Mac OS X, Win32...)
+
* Platform and compiler (Linux, Mac OS X, Win32...).
* Attach a save game if possible
+
* Attach a save game if possible.
* Attach a screenshot to demonstrate graphics bugs if applicable
+
* Attach a screenshot to demonstrate graphics bugs if applicable.
  
 
It may happen that at some point of our testing we break savegame compatibility, or do something which affects a specific engine deeply. In that case, you could be asked to restart the game you're currently playing from the beginning. You will be explicitly told to do so, so don't worry if we say nothing in this aspect.
 
It may happen that at some point of our testing we break savegame compatibility, or do something which affects a specific engine deeply. In that case, you could be asked to restart the game you're currently playing from the beginning. You will be explicitly told to do so, so don't worry if we say nothing in this aspect.
  
Please, report about your completion on scummvm-devel@lists.sourceforge.net, on our forums either talk to some developer (an op) at #scummvm on irc.freenode.net. If you encountered some problem, provide the bug report number as well.
+
Please, report about your completion on our forums (preferably in the thread linked by the testing announcement). If you encountered some problem, provide the bug report number as well.
  
 
Thanks for your help.
 
Thanks for your help.

Latest revision as of 00:08, 23 November 2017

Release Testing for ScummVM

Testing Guidelines

  • Use the latest build which you may find at the bottom of our download page. After we branched please use the latest stable builds when downloading from our Buildbot.
  • Use the launcher to add your game and see if it was detected normally, even if you already have this game already added. Start newly added target.
  • Preferably test detection of every game/demo you have, even when you're not going to play them.
  • Play game from beginning through the end.
  • Preferably use of save/load facility.
  • Do not skip cutscenes.
  • If you encounter any problems, please, submit a bug report at our bug tracker.
  • If a game has several branches, test as many variants as you can.
  • At least 1 user should test each game, preferably but not obligatory on different platforms.
    • However, more than one user should test games that satisfy one or more of the following conditions:
      • It is a multiple path game (such as Fate of Atlantis or Maniac Mansion). We designate such games with a # (hash symbol).
      • It is a new game for this release. We designate such games with a * (star symbol).

What to provide when you encounter a bug

Please provide information on our bug tracker. Please, do not post bugs to our forums as that makes discussions and bug fixing progress tracking practically impossible.

  • Make sure that you have a working mail set up at your GitHub account. In this case you will receive our reply to your bug report.
  • Snapshot date (but please, always test with the latest one).
  • Bug details, including instructions on reproducing it.
  • Language of game (English, German...).
  • If it is a fan translation, mention it.
  • Version of game (talkie, floppy...).
  • Whether the sound was compressed or not.
  • Platform and compiler (Linux, Mac OS X, Win32...).
  • Attach a save game if possible.
  • Attach a screenshot to demonstrate graphics bugs if applicable.

It may happen that at some point of our testing we break savegame compatibility, or do something which affects a specific engine deeply. In that case, you could be asked to restart the game you're currently playing from the beginning. You will be explicitly told to do so, so don't worry if we say nothing in this aspect.

Please, report about your completion on our forums (preferably in the thread linked by the testing announcement). If you encountered some problem, provide the bug report number as well.

Thanks for your help.