seeder_tests is vague and does not properly describe what is being
tested. p2p_messaging_tests better describes what is being
tested.
Details
Details
- Reviewers
jasonbcox - Group Reviewers
Restricted Owners Package (Owns No Changed Paths) Restricted Project - Commits
- rSTAGINGd50368de0819: Rename seeder_tests to p2p_messaging_tests
rABCd50368de0819: Rename seeder_tests to p2p_messaging_tests
make check ninja check ninja check-bitcoin-seeder
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- RenameSeederTests
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 9703 Build 17299: Default Diff Build & Tests Build 17298: arc lint + arc unit
Event Timeline
Comment Actions
message_processing_tests is a clear artifact from the code that doesn't actually tell us much, but does raise questions. What kind of messages? What "processing" is going on? Why not something like p2p_message_tests? It answers the first question, although the second is not really that interesting since again, that part is an artifact from the implementation.