From Fedora Project Wiki
< QA
(Software Quality Best Practices - documentation) |
m (→Motivation) |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 3: | Line 3: | ||
== Motivation == | == Motivation == | ||
This section focuses on Best Practices for improving quality of open source | This section focuses on Best Practices for improving quality of open source software. Get inspiration how to create test harness for your application and how to alter your software development model to produce bug-free code. | ||
== Development model == | == Development model == | ||
Hints for altering your development model to match SW quality | Hints for altering your development model to match SW quality standards. | ||
== Test suite implementation == | == Test suite implementation == | ||
Learn how to write effective unit test depending on your | Learn how to write effective unit test depending on your application native language: | ||
* python | * python | ||
* perl | * perl | ||
* C | * C | ||
* Java | * C++ | ||
* Java | |||
* shell (bourne, korn) | |||
== Events == | == Events == | ||
2008-12- | 2008-12-11: PyUnit Workshop | ||
== Links == | == Links == | ||
* http://googletesting.blogspot.com/2008/11/clean-code-talks-unit-testing.html | |||
* http://googletesting.blogspot.com/2008/11/my-unified-theory-of-bugs.html |
Latest revision as of 10:18, 1 April 2009
Software Quality Best Practices
Motivation
This section focuses on Best Practices for improving quality of open source software. Get inspiration how to create test harness for your application and how to alter your software development model to produce bug-free code.
Development model
Hints for altering your development model to match SW quality standards.
Test suite implementation
Learn how to write effective unit test depending on your application native language:
- python
- perl
- C
- C++
- Java
- shell (bourne, korn)
Events
2008-12-11: PyUnit Workshop