Changes between Version 2 and Version 3 of Topics-2010-05-20
- Timestamp:
- 05/20/10 12:49:21 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Topics-2010-05-20
v2 v3 5 5 Should we start configuring a dedicated testing framework for OpenVPN? This idea will be presented by ''mattock''. 6 6 7 '''Rationale''' 7 * '''Rationale''' 8 * Would allow testing that OpenVPN works on a large number of predefined platforms and configurations 9 * Replaces part of the manual testing effort by testing the external behavior of the application automatically 10 * Would allow spotting bugs early 8 11 9 Would allow testing that OpenVPN works on a large number of predefined platforms and configurations with ''minimal manual effort'' (after initial setup). Would allow spotting bugs early. 10 11 '''Limitations'' 12 13 Only tests for external behavior of the application. Does not replace human testing when problems are complex, e.g. dependent on complex interaction of configuration parameters or components. 12 * '''Limitations''' 13 * Only tests for external behavior of the application 14 * Does not replace human testing when problems are complex, e.g. dependent on complex interaction of configuration parameters or components. 14 15 15 16 == Continuous integration server == … … 17 18 Should we build a continuous integration / automated release management server? This idea will be presented by ''mattock''. 18 19 19 '''Rationale''' 20 * '''Rationale''' 21 * Would allow spotting build problems early on by building "allmerged" and reporting developers of build problems 22 * Would reduce developer frustration 23 * Would allow automated packaging of openvpn-testing for various platforms and publishing those on a web server 24 * 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 25 * Could also allow centralized automated searching of code problems 20 26 21 Would allow spotting build problems early on by building "allmerged" and reporting developers of build problems. Would allow automated packaging of openvpn-testing for various platforms and publishing those on a web server. This in turn would 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. 27 * '''Limitations''' 28 * Does not replace human testing 29 * Only tests the build process (and possibly code problems) 22 30 23 31 == Developer bounties ==