[openssl-dev] Code Health Tuesday - test modernisation

[Paul Dale]

Next week on the 11th of April it is Code Health Tuesday again.

 

This fortnight it will be about updating the C unit tests to use the test framework. Everyone is invited to participate to help bring consistency and order to the unit tests.

                                                                                                                                            

Many of the existing C tests are ad-hoc.  The desired form of C test executables is described at the end of test/README.  A brief description of the condition and output framework is in the list archives: https://www.mail-archive.com/openssl-dev@openssl.org/msg46648.html.  Some tests have already been updated to use both to serve as examples.

 

 

Regards,

 

Pauli

(at the suggestion of the dev team)

 

 

FAQ:

 

Q: How do I participate?

A: Once you've update your tests, create a Github pull request and put "code health" in the title. Such commits will be monitored for quick turnaround.

 

Q: Which tests should I convert?

A: There is a spreadsheet: conversion: https://docs.google.com/spreadsheets/d/1VJTmEVT1EyYxZ90GnhAPd4vtFg74Ij3Y-pthjXdmH80/edit#gid=0 This lists all the C tests, select one you want to work on and tag it to avoid duplication.

 

Q: Which branch should I target?

A: Master is the one.  It is the only branch with the new infrastructure.

 

Q: Where do I go if the infrastructure isn't working?

A: Post the problem here.

 

Q: Can I suggest improvements to the infrastructure?

A: Sure thing, post them here too.

 

 

-- 

Oracle

Dr Paul Dale | Cryptographer | Network Security & Encryption 

Phone +61 7 3031 7217

Oracle Australia

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-dev/attachments/20170405/c7ca3071/attachment.html>