Skip to content
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

Open
swinslow opened this issue Dec 17, 2018 · 5 comments
Open

Add test scripts and CI #13

swinslow opened this issue Dec 17, 2018 · 5 comments
Labels
enhancement New feature or request

Comments

@swinslow
Copy link
Contributor

Currently, the fossdriver repo does not include any test scripts or CI integration. Prior to an official release, it should include:

  • scripts to enable spinning up a test Fossology server (presumably using the Fossology docker images)
  • CI integration (perhaps Travis CI?)
  • testing scripts to run through fossdriver functionality and ensure it works against the Fossology test server)

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.

@swinslow swinslow added the enhancement New feature or request label Dec 17, 2018
@sjha2048
Copy link

sjha2048 commented Mar 2, 2020

Hi @swinslow , I would like to work on this issue, can you please assign it to me?

@swinslow
Copy link
Contributor Author

swinslow commented Mar 2, 2020

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!

@sjha2048
Copy link

sjha2048 commented Mar 2, 2020

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?

@sjha2048
Copy link

sjha2048 commented Mar 2, 2020

needed some more clarification on the testing part.

@swinslow
Copy link
Contributor Author

swinslow commented Mar 3, 2020

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants