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

Timestamp:

05/21/10 07:51:41 (14 years ago)

Author:

Samuli Seppänen

Comment:

--

Topics-2010-05-20

@@ -10 +10 @@
   * Would allow spotting bugs early
 
+ * '''Implementation ideas'''
+  * 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).
+
  * '''Limitations'''
   * Only tests for external behavior of the application
@@ -19 +22 @@
 
  * '''Rationale'''
-  * Would allow spotting build problems early on by building "allmerged" and reporting developers of build problems (by email?)
+  * Would allow spotting build problems early on by building "allmerged" and reporting developers of build problems
   * Would reduce developer frustration
   * Would allow automated packaging of openvpn-testing for various platforms and publishing those on a web server
   * 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
   * Could also allow centralized automated searching of code problems
-   * 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.
+
+ * '''Implementation ideas'''
+  * Developers could be notified of problems using email
+  * 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.
 
  * '''Limitations'''