Changes between Version 9 and Version 10 of Topics-2010-05-20


Ignore:
Timestamp:
05/21/10 07:51:41 (10 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Topics-2010-05-20

    v9 v10  
    1010  * Would allow spotting bugs early
    1111
     12 * '''Implementation ideas'''
     13  * Beaker could perhaps be made to simulate poor connections for testing purposes. If not, there are a plenty of tools and services available for this purpose (see full chatlog).
     14
    1215 * '''Limitations'''
    1316  * Only tests for external behavior of the application
     
    1922
    2023 * '''Rationale'''
    21   * Would allow spotting build problems early on by building "allmerged" and reporting developers of build problems (by email?)
     24  * Would allow spotting build problems early on by building "allmerged" and reporting developers of build problems
    2225  * Would reduce developer frustration
    2326  * Would allow automated packaging of openvpn-testing for various platforms and publishing those on a web server
    2427  * The above would translate to increased use of openvpn-testing, leading to earlier bug reports and would thus make the release process (new code -> acceptance to testing -> acceptance to stable -> release) faster
    2528  * Could also allow centralized automated searching of code problems
    26    * The OpenVPN project has a license to [http://www.coverity.com/ Coverity] service. As this service has an API, Coverity code analysis could be integrated to the CI server.
     29
     30 * '''Implementation ideas'''
     31  * Developers could be notified of problems using email
     32  * The OpenVPN project has a license to [http://www.coverity.com/ Coverity] service. As this service has an API, Coverity code analysis could be integrated to the CI server.
    2733
    2834 * '''Limitations'''