Turbo Integration testing
@clc,
Turbo has been packaged for easy install, documented, integrated into libEHP, and likely is ready for integrating into a second project. @an7s and I have discussed and think you doing "yaml-cpp" is the right second project.
Pros:
- Yaml-cpp is "real" software.
- We use it and have the source.
- It's widely used and will be understandable by the AF
- Nicely fits the turbo model
- Your eyes are relatively "fresh" to Turbo compared to anyone else in the group
Cons:
- It's not "our" software, so we may end up reporting bugs we find and having to deal with that somehow.
We'd like you to do it because fresh eyes help find issues in the install/documentation process. This endeavor is partly a test of the documentation, so I'd prefer not to (directly) answer "how to" questions about using Turbo. If the docs are unclear or insufficient, let me know and I'll update them to get you un-stuck. If we find bugs in Turbo, we'll fix and re-deploy to get you un-stuck.
Notes:
- Turbo docs here: Turbo Wiki
- Billing to KR Phase 1, @jwd
- You'll need a "fresh" machine. I'll create a VM in openstack for you and give you access info in a comment below.
- Please don't make any changes to the yaml-cpp project directly. Let's make a fork of that project for our turbo/testing additions.
- We do not want to fuzz yaml-cpp as a library, as libEHP already covers that use case.
- If yaml-cpp has internal tests, maybe we can use them. If not, statically link yaml-cpp into a main executable and hook it up to standard out to follow the gzip tutorial in the turbo wiki.
-j
Edited by Jason Hiser