Overview of the Feature Request
A GitHub Actions that runs tests against the JSF Frontend. There is a testing repository: https://github.com/uncch-rdmc/kunai-runner
that UNC RDMC uses to validate its Dataverse installations. Instead of directly merging the code into upstream and creating a split-brain or submodule/subtree scenario, it might be in upstream's best interest to outsource the suite to a different repository and keep the GitHub Action instead.
What kind of user is the feature intended for?
Every developer and engineer who runs a Dataverse Installation will find active use for this action and this testing suite.
What inspired the request?
UNC's own needs require testing our installations for 21 CFR Part 11 compliance, we decided to open source the testing suite.
What existing behavior do you want changed?
N/A
Any brand new behavior do you want to add to Dataverse?
N/A
Any open or closed issues related to this feature request?
N/A
Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?
Yes, our organization will be actively maintaining both this GitHub Action and the testing suite behind this GitHub Action. Although it was designed to be private, the public facing suite is entirely courtesy of @donsizemore and @uncch-rdmc. Thank you!
Overview of the Feature Request
A GitHub Actions that runs tests against the JSF Frontend. There is a testing repository: https://github.com/uncch-rdmc/kunai-runner
that UNC RDMC uses to validate its Dataverse installations. Instead of directly merging the code into upstream and creating a split-brain or submodule/subtree scenario, it might be in upstream's best interest to outsource the suite to a different repository and keep the GitHub Action instead.
What kind of user is the feature intended for?
Every developer and engineer who runs a Dataverse Installation will find active use for this action and this testing suite.
What inspired the request?
UNC's own needs require testing our installations for 21 CFR Part 11 compliance, we decided to open source the testing suite.
What existing behavior do you want changed?
N/A
Any brand new behavior do you want to add to Dataverse?
N/A
Any open or closed issues related to this feature request?
N/A
Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?
Yes, our organization will be actively maintaining both this GitHub Action and the testing suite behind this GitHub Action. Although it was designed to be private, the public facing suite is entirely courtesy of @donsizemore and @uncch-rdmc. Thank you!