Edgewall Software

Changes between Version 79 and Version 80 of TracDev/ReleaseTesting


Ignore:
Timestamp:
May 21, 2015, 11:52:59 AM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/ReleaseTesting

    v79 v80  
    11= Release Testing
    22
    3 To ensure that our releases are well tested and as bug free as possible we need your help.
     3To ensure that our releases are well tested and with as few bugs as possible, we need your help.
    44
    55If you have a Trac installation with a combination of OS, database or frontend not represented in the list below, please consider adding yourself to the list.
     
    77== What's expected of me?
    88
    9 At the beginning of the release testing period you will be added to the CC-list of the release ticket, where you will find details on where to download the release candidate. The ticket might also mention additional information on specific areas/features to test. But in most cases it's enough to verify that the release works as expected on your system. Running the [TracDev/UnitTests unit tests] and [TracDev/FunctionalTests functional tests] and getting a green light would be a plus.
     9At the beginning of the release testing period you will be added to the CC-list of the release ticket, where you will find details on where to download the release candidate. The ticket might also mention additional information on specific areas/features to test. But in most cases it is enough to verify that the release works as expected on your system. Running the [TracDev/UnitTests unit tests] and [TracDev/FunctionalTests functional tests] and getting a green light would be a plus.
    1010See [#TestingScenarios Testing Scenarios] below for some suggestions.
    1111
     
    1313
    1414== Current target releases
     15
    1516 - [milestone:0.12.7]
    1617 - [milestone:1.0.7]
     
    2021== Systems
    2122
    22 ||=Contact=||\
    23 ||=Python=||\
    24 ||=Database Backend + Bindings=||\
    25 ||=Genshi=||\
    26 ||=Web Frontend=||\
    27 ||=OS=||\
    28 ||=Subversion, Git=||\
    29 ||=Testing=||
     23||='''Contact'''=||\
     24||='''Python'''=||\
     25||='''Database Backend + Bindings'''=||\
     26||='''Genshi'''=||\
     27||='''Web Frontend'''=||\
     28||='''OS'''=||\
     29||='''Subversion, Git'''=||\
     30||='''Testing'''=||
    3031|------------------------------------------------------------------------------------
    3132||  JonasBorgstrom \\ ChristianBoos \\ *.edgewall.org ||\
     
    4950|| SQLite 3.7.5 (PySqlite 2.6.0) || \
    5051|| 0.6 || \
    51 || apache 2.0.59 + mod_wsgi 3.3 || \
     52|| Apache 2.0.59 + mod_wsgi 3.3 || \
    5253|| SuSE SLES 9.3 x86_64, xfs || \
    5354|| svn 1.7.5 || \
     
    322323|------------------------------------------
    323324
    324 ''Please indicate your e-mail address under "Contact".''
     325When adding yourself and your test configuration to the list, please also indicate your e-mail address under "Contact".
    325326
    326327== Testing Scenarios
    327 The above configurations are used in to the following test conditions, along with corresponding expectations.
    328 === ''prod''
    329  - version is used in "production", on a heavily used site (public or private)
    330  - no regression or new defect should be reported by the users
    331 === ''dev''
    332  - full test suite pass (both unit tests and functional tests)
    333  - testing creation of a new environment, using a Trac mirror for the repository
    334  - interactive testing of that new environment
    335  - memory usage should stay steady and performance should be adequate
    336 === ''devlite''
    337  - full test suite pass (both unit tests and functional tests)
    338  - interactive testing of existing environment
    339  - memory usage should stay steady and performance should be adequate
    340 
    341 (expand as needed)
     328
     329The above configurations are used in the following test conditions, along with corresponding expectations.
     330
     331=== prod
     332
     333 - Version is used in "production", on a heavily used site, either public or private.
     334 - No regression or new defect should be reported by the users.
     335
     336=== dev
     337
     338 - Full test suite pass, both unit tests and functional tests.
     339 - Testing creation of a new environment, using a Trac mirror for the repository.
     340 - Interactive testing of that new environment.
     341 - Memory usage should stay steady and performance should be adequate.
     342
     343=== devlite
     344
     345 - Full test suite pass, both unit tests and functional tests.
     346 - Interactive testing of existing environment.
     347 - Memory usage should stay steady and performance should be adequate.
     348
     349'''Note''': expand as needed.