Move testing to GenericGraph

[gdalle]

We recently introduced two types called GenericGraph and GenericDiGraph that wrap a SimpleGraph or a SimpleDiGraph. These generic types try to fulfill the AbstractGraph interface in a minimal way, while having no other methods implemented. The idea is then to test functions that can take an AbstractGraph with these generic types instead of simple graphs, in order to verify that they would indeed work with any AbstractGraph.
Similar things can be found in the Julia standard library, for example Test.GenericArray and Test.GenericString.

Now we need to change our tests, so that they use the generic graph types, and try to spot and fix bugs that occur during that process. It is probably not possible to do this for all functions, but at least we can spot the places where that is the case.

Some progress has already been done or at least started in:

• test/biconnectivity Use GenericGraph for testing biconnectivity algorithms #270
• test/centrality Test centrality with generic graph #272
• test/community Test community with generic graph #273
• test/cycles Test cycles with generic graph #274
• test/shortestpaths Use GenericGraph for testing shortestpaths algorithms #275
• test/spanningtrees Use GenericGraph for testing spanningtrees algorithms #276
• test/connectivity.jl Tests for various files with generic graph #278
• test/core.jl Tests for various files with generic graph #278
• test/degeneracy.jl Tests for various files with generic graph #278
• test/distance.jl Tests for various files with generic graph #278
• test/edit_distance.jl Tests for various files with generic graph #278
• test/operators.jl Tests for various files with generic graph #278

[simonschoelly]

I don't think this should be tagged as a v2.0 issue, there is no reason not to use GenericGraph right now.

[gdalle]

Fair enough

[gdalle]

@simonschoelly is there any more we can do on this end? I would keep the issue open though