Difference between revisions of "Unit Testing"
(→Team) |
(→Howtos) |
||
Line 24: | Line 24: | ||
The current list is posted in the [http://goo.gl/5u9nbw OpenSSL Testing Tasks Google Spreadsheet]. | The current list is posted in the [http://goo.gl/5u9nbw OpenSSL Testing Tasks Google Spreadsheet]. | ||
− | == Howtos == | + | == Howtos and Style Guides == |
Documents that provide background on specific testing issues and idioms should be linked from here. | Documents that provide background on specific testing issues and idioms should be linked from here. | ||
Revision as of 20:32, 4 June 2014
This page will track the effort to improve unit test and other automated test coverage for OpenSSL. Everyone is encouraged to help with this effort, but this page will track which community members have accepted specific responsibilities, and what tasks are currently underway.
Team
We can define new roles as needed. The success of this effort will be inversely proportional to the number of roles with any one individual's name next to them. Each role can have more than one person filling it, but needs specific people to fill them.
The point is not to tell people what to do and not do: it’s to establish clear responsibilities so everyone can run with them right away and begin applying their creative energy to solutions, rather than waste it figuring out what the hell is going on, what they should do to contribute, and who they need to coordinate with to get things done.
Organizer: Mike Bland
Ensures the overall effort is making progress by facilitating communication, removing obstacles, and making hands-on contributions when necessary.
Tech Writer: Mike Bland, Chelsea Komlo
Maintains documentation of tools, techniques, outstanding issues, etc. May maintain a code review/testing style guide based on the community consensus. Also documents who currently fills each role, as well as who might've filled it in the past.
Buildmaster: Mike Bland, Isaac Truett
Sets up and maintains automated builds and any infrastructure used to monitor them and report breakage.
Toolsmith: Tony Aiuto Maintains any tools and frameworks that are a part of the core build process; proposes, integrates, and/or retires existing tools.
Tutor: Mike Bland, Darshan Mody, Tom Francis, Brian N. Makin, Sandeep Mankar, Chelsea Komlo, Edward Knapp
Helps contributors, particularly new contributors, with the details of writing unit or other automated tests. May be assigned by the reviewer of a patch to help a contributor get a new change under test. Submission of the patch should require the approval of the tutor in most cases. (Should ideally be more than one person.)
Tasks
The current list is posted in the OpenSSL Testing Tasks Google Spreadsheet.
Howtos and Style Guides
Documents that provide background on specific testing issues and idioms should be linked from here.
Samples
Existing tests that can be used as models for new tests.