-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add test scripts and CI #13
Comments
Hi @swinslow , I would like to work on this issue, can you please assign it to me? |
Hi @sjha2048, can you provide some thoughts on the approach you plan to take? Happy to assign it but just hoping to see some details about the plan that you have in mind, so that it doesn't deter other folks from working on it too. Thanks and I appreciate your offer to help! |
Thanks for replying, for starting off I was planning to dockerize fossdriver and CI integration(I found it pretty similar to Atarashi) using Travis as fossology also uses Travis, perhaps we can split this issue into several issues for implementing the test scripts? |
needed some more clarification on the testing part. |
Makes sense to split into separate issues for some of the precursor steps, in particular if you're planning to put together a Dockerfile for fossdriver. Feel free to file an issue and to start putting together PRs for any of this. The test scripts will be the main part of this though. What sorts of tasks have you used fossdriver for, so far? How have you been using it in Fossology workflows? |
Currently, the fossdriver repo does not include any test scripts or CI integration. Prior to an official release, it should include:
As a bonus, this could also be set up to test against multiple versions of Fossology, to help ensure that fossdriver stays current if/when the Fossology interface changes.
The text was updated successfully, but these errors were encountered: