-
Notifications
You must be signed in to change notification settings - Fork 995
Open
0 / 10 of 1 issue completedOpen
0 / 10 of 1 issue completed
Copy link
Labels
containersRelated to augur in containers, container images, or the compose file, either in podman or in dockerRelated to augur in containers, container images, or the compose file, either in podman or in dockertestingRelated to Augur's testing suiteRelated to Augur's testing suite
Description
In addition to our smoke tests, I wonder if we could incorporate a new kind of test that either replaces, or adds onto it.
This test would:
- start up augur/initialize a DB very much like the smoke tests.
- somehow sneak in and mark the augur/augur repo as IGNORE (its too big to and takes too long to collect, would waste github resources)
- run for a few mintues - enough for comfortably finishing a full collection on some of our smaller default repos. (this may require introducing a special command line flag or something into augur to have it stop and shut itself down once it hits full collection and all tasks go idle)
- run some queries to validate the results, such as:
- checking that chaoss/whitepaper was automatically ignored
- checking that all commits in the commits table have proper author names etc (regression test)
- checking that an appropriate number of contributors got resolved
- run the self test?
- anything else?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
containersRelated to augur in containers, container images, or the compose file, either in podman or in dockerRelated to augur in containers, container images, or the compose file, either in podman or in dockertestingRelated to Augur's testing suiteRelated to Augur's testing suite