#12597 closed Feature Requests (fixed)
Report tests with clashing names
| Reported by: | Owned by: | Raffi Enficiaud | |
|---|---|---|---|
| Milestone: | Boost 1.67.0 | Component: | test |
| Version: | Boost 1.62.0 | Severity: | Problem |
| Keywords: | Cc: |
Description
It's possible right now for two different tests to have the same name. This is a problem for test runners, since there's no way to run a specific test if there are other tests with the same name. Boost.Test should detect tests with clashing names on startup and report an error, similar to how Google Test and Catch do that.
Change History (10)
comment:1 by , 6 years ago
| Type: | Bugs → Feature Requests |
|---|
comment:3 by , 5 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 5 years ago
| Milestone: | To Be Determined → Boost 1.66.0 |
|---|
comment:5 by , 5 years ago
| Milestone: | Boost 1.66.0 → Boost 1.67.0 |
|---|
comment:8 by , 4 years ago
I can open another bug report if necessary, but it seems this patch has also made it impossible to have multiple test *suites* of the same name, if defined in multiple translation units.
I understand the rationale for ensuring no tests themselves have the same name, but we regularly define tests that belong to the same suite in different translation units using BOOST_AUTO_TEST_SUITE(...).
Is there a way we can get the enforcement relaxed to only care about tests and not the test suites?
comment:9 by , 4 years ago
I am sorry about that! I thought I had this covered already. It would be great if you file a new bug report. Thanks!
comment:10 by , 4 years ago
I am not able to reproduce this problem of defining multiple test suites with same name with BOOST_AUTO_TEST_SUITE
In branch
topic/12597-report-tests-with-clashing-names