Test framework of choice for project?

[lordofhyphens]

Continuing the conversation from #9.
Some questions:

Do we feel like we need to add tests for device code?
Do we want to include the test framework as a submodule (if possible)? Just list it as a dependency for the user to figure out installation on their own?

[harrism]

Tests should test functionality of Hemi. If Hemi provides device code, then it should be tested. I think since Tests won't be a requirement for users to use the library, the framework can just be listed as a dependency.

[lordofhyphens]

Fair enough.

[harrism]

Actually now that I know how git submodules work, putting the test framework as a submodule works well, since it only gets the files when you git submodule update. But then again I don't know if google test is available on git.

[lordofhyphens]

It's not that I'm aware of, but it would be possible to just clone the svn repo and leave a copy on github (BSD 3-clause). Which has been done many, many times.
https://github.com/search?q=googletest&ref=cmdform

Here's one that was updated recently: https://github.com/liquid-mirror/googletest

[harrism]

googletest is now a submodule. Closing.