[ENH] Python tests should have a shared set of fixtures

[rlratzel]

Many of the tests do very similar setup steps, including iterating over a set of datasets, creating a specific graph type, creating a specif Nx graph type, running an algo and checking/comparing results. The steps prior to running the algo are almost identical across most tests, yet each test has its own set of fixtures.

The shared util file defines the dataset params (which is good), but the actual fixtures could be shared as well. This should allow for a great deal of cleanup when applied to all python tests.

• Add/update a fixture for reading in datasets and returning a graph object
  • For use with all datasets, subset of datasets, etc.
  • Have pytest options for which datasets to run
  • Add this to a shared “fixtures” module, configured to scope “session”
• Add/update a fixture for returning a Nx graph object
  • Calls fixture above to read in dataset and return cugraph obj
  • Add this to a shared “fixtures” module, configured to scope “session”
• Add/update a fixture for per-algo Nx runs with params for comparisons
  • Unique to a particular algo comparison (scope=”module”)

[github-actions[bot]]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

[github-actions[bot]]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

[rlratzel]

This is on-hold but should be addressed in upcoming refactorings.

[github-actions[bot]]

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

[github-actions[bot]]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

[rlratzel]

Some of the proposed changes mentioned here have either been done for a subset of tests or are still being planned. Since this issue is relatively stale, we'll close it and re-open as one or more smaller issues when we're closer to continuing work on these changes.