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

CI/CD integration of anonymizer script testing #58

Open
jdonenine opened this issue Nov 24, 2020 · 2 comments · May be fixed by #160
Open

CI/CD integration of anonymizer script testing #58

jdonenine opened this issue Nov 24, 2020 · 2 comments · May be fixed by #160
Assignees
Labels
medium tech-debt Technical debt

Comments

@jdonenine
Copy link
Contributor

jdonenine commented Nov 24, 2020

Integrate testing of the anonymizer script into CI/CD pipelines.

To standardize with other community projects (k8ssandra) it would be ideal if we can achieve this using GH Actions.

┆Issue is synchronized with this Jira Task by Unito
┆Issue Number: AD-101

@jdonenine jdonenine added the tech-debt Technical debt label Nov 24, 2020
@jdonenine jdonenine added this to the Automated NoSQLBench Integration milestone Jan 12, 2021
@jdonenine jdonenine modified the milestones: Automated NoSQLBench Integration, Backlog, Integrity Testing Feb 22, 2021
@jdonenine jdonenine removed this from the Integrity Testing Enhancements milestone Jun 7, 2021
@jdonenine
Copy link
Contributor Author

Focused on the python tooling, automation of:

  • Unit Tests
  • Integration Tests

@absurdfarce
Copy link
Collaborator

It looks like this can be pretty easily accomplished with Actions but we'll probably want to hold off until #152 is merged. That PR significantly changes the requirements + process for running the Python test suite; not really much point in setting up Actions for some other approach when it's just gonna be changed once 152 hits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
medium tech-debt Technical debt
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants