Improve the topology test suite
See original GitHub issueSince we had some issues with testing in the past, I propose that we include the hypothesis
module for Python into our test suite. Side by side with the pytest
module we’re already running as it is compatible with pytest
. The hypothesis
module allows us to cover a broader range in our parametrization and checks edge cases. As they say it on their page:
It lets you write tests which are parametrized by a source of examples, and then generates simple and comprehensible examples that make your tests fail. This lets you find more bugs in your code with less work.
It is quite powerful and might help us in finding bugs earlier.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
UnitTesting - NFD - NDN project issue tracking system
Boost Unit Test Framework documentation; After compiling the test binary (or binaries), it is possible at run time to select which tests to...
Read more >MPI Test Suite Test Descriptions - HPC Centers - HPCMP
The Network topology tests are designed to examine the operation of specific communication patterns such as Cartesian and Graph topology.
Read more >phoronix-test-suite/phoronix-test-suite.md at master - GitHub
Phoromatic is a remote management system for the Phoronix Test Suite that allows the automatic scheduling of tests, remote installation of new tests,...
Read more >Tests in MDAnalysis
Use classes to group tests if it makes sense (e.g., if the test class will be inherited by another test class and the...
Read more >How to Effectively Prepare “Test Bed” and Minimize the Test ...
This article talks about what exactly the Test Bed entails: It is a two-step process of Test Environment setup and Test Data setup....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, exactly! But now we use it for the topology tests. We just have to return the history and the best cost/pos in the fixture so we can check if it really is the best that has ever been found. I’ll go ahead and write this up. It’s probably a small PR.
Sorry it’s not yet clear to me. How is this different from our
*_opt_history()
fixtures? Can we reuse these fixtures for the problem? 👍