GroteGnoom

igraph_vss_adj only has a declaration, but nothing else, so I think its declaration and its mention here can be removed.

next: igraph_laplacian_spectral_embedding (https://igraph.discourse.group/t/the-unit-tests-thread/597/48) igraph_local_scan_k_ecount (doesn't handle loops correctly, should be fixed) igraph_hsbm_game (needs some reading or outside help to understand)

igraph_sparsemat_nonzero_storage is tested in #1680 all 6 rng functions are tested in #1675 igraph_progress_handler_stderr and igraph_set_progress_handler are tested in #1674 igraph_layout_drl is tested in #1670 igraph_layout_graphopt is tested in #1668...

igraph_progress_handler_stderr and igraph_set_progress_handler can be crossed off the list. also igraph_strvector set2, remove and print (#1691) Also, some questions: > Tests should be written for some of these functions. Does...

> This is going to be somewhat subjective though. Of course! :slightly_smiling_face: But much better than not prioritizing. You can also be 'conservative', but then at least skip testing things...

Yes, I'll do that one soon 🙂

igraph_maximum_cardinality_search now seems pretty thoroughly tested because of the is_chordal tests, so I think it can be removed from the list. Or is there still a reason to test it...

I've removed the 'good first issue' label, because there are only special cases left, like undocumented or unnecessary functions.

For easier reference: Fixes #1840

I don't think I have the time to go through everything thoroughly, but I'll at least add some comments :)