test: filling gaps in MAS and SW - #569
Conversation
|
Boost dependency footprint vs Header-inclusion weights (graph files pulling each direct dependency in): No header-inclusion-weight changes. Transitive Boost modules: 68 → 68 (0) |
|
Compiler-warning counts vs
|
817b58a to
002b0ae
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! 🚀 New features to boost your workflow:
|
87186f5 to
1aec9e2
Compare
| std::mt19937 rng(static_cast< std::mt19937::result_type >(seed)); | ||
| const undirected_graph g = mas_sw_oracle::make_random_connected_graph(n, n, rng); | ||
| BOOST_TEST(mas_sw_oracle::is_connected(g)); |
There was a problem hiding this comment.
I know this practice is probably widespread in BGL, but I'm generally against using randomness in unit tests. What we want is careful selection of inputs that trigger different conditions inside the algorithms. Fuzzing has its place, but not here.
There was a problem hiding this comment.
Oh ? You want to manually define inputs ? I think I agree with the idea, but practically what if outputs are not trivial given the input ? And how to test for scale effects ?
1aec9e2 to
1a4d086
Compare
1a4d086 to
162a82b
Compare
162a82b to
62e4282
Compare
Adding test support before tackling fixes:
#297
#286
Before submitting
developbranch.Type of change
Adding tests.
Does this PR introduce a breaking change?
What this PR does
Motivation
Testing
Checklist
b2in thetest/directory).