port unittests to boost::test
Bug #667162 reported by
Monty Taylor
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Fix Released
|
Low
|
Andrew Hutchings | ||
| 7.0 |
Fix Released
|
Low
|
Andrew Hutchings | ||
Bug Description
The unittests are using google test. At the time, we chose that because the minimum boost version we accepted was too early for boost::test to be sensibly used, but at that time there were no other real differences found.
The API is almost identical... and since we already require boost, it would make more sense to remove the gtest requirement and just use boost.
Related branches
lp:~linuxjedi/drizzle/trunk-unittests
- Drizzle Developers: Pending requested
-
Diff: 7218 lines (+200/-3799)27 files modifiedconfigure.ac (+1/-1)
docs/installing/from_source.rst (+1/-1)
docs/installing/requirements.rst (+2/-1)
m4/pandora_have_libboost_test.m4 (+45/-0)
m4/pandora_have_libgtest.m4 (+0/-47)
unittests/atomics_test.cc (+73/-87)
unittests/calendar_test.cc (+47/-47)
unittests/client_server.c (+0/-567)
unittests/constrained_value.cc (+0/-57)
unittests/date_test.cc (+0/-522)
unittests/date_time_test.cc (+0/-460)
unittests/generators.cc (+0/-72)
unittests/global_buffer_test.cc (+0/-60)
unittests/include.am (+8/-16)
unittests/libdrizzle_test.cc (+0/-59)
unittests/main.cc (+23/-12)
unittests/micro_timestamp_test.cc (+0/-108)
unittests/nano_timestamp_test.cc (+0/-97)
unittests/option_context.cc (+0/-56)
unittests/pthread_atomics_test.cc (+0/-134)
unittests/table_identifier.cc (+0/-88)
unittests/temporal_format_test.cc (+0/-151)
unittests/temporal_generator.cc (+0/-195)
unittests/temporal_interval_test.cc (+0/-230)
unittests/time_test.cc (+0/-381)
unittests/timestamp_test.cc (+0/-262)
unittests/utf8_test.cc (+0/-88)
| Changed in drizzle: | |
| milestone: | none → ongoing |
| tags: | added: low-hanging-fruit |
| Changed in drizzle: | |
| importance: | Undecided → Low |
| Changed in drizzle: | |
| status: | New → Confirmed |
| Changed in drizzle: | |
| assignee: | nobody → Andrew Hutchings (linuxjedi) |
Revision history for this message
| Patrick Crews (patrick-crews) wrote Re: [Bug 667162] Re: port unittests to boost::test | #1 |
To post a comment you must log in.
3 cheers to you, sir. Thanks for taking this on : )
On Mon, Dec 20, 2010 at 2:29 PM, Andrew Hutchings <<email address hidden>
> wrote:
> ** Changed in: drizzle
> Assignee: (unassigned) => Andrew Hutchings (linuxjedi)
>
> --
> You received this bug notification because you are a member of Drizzle-
> developers, which is subscribed to Drizzle.
> https:/
>
> Title:
> port unittests to boost::test
>
> Status in A Lightweight SQL Database for Cloud Infrastructure and Web
> Applications:
> Confirmed
>
> Bug description:
> The unittests are using google test. At the time, we chose that because
> the minimum boost version we accepted was too early for boost::test to be
> sensibly used, but at that time there were no other real differences found.
>
> The API is almost identical... and since we already require boost, it would
> make more sense to remove the gtest requirement and just use boost.
>
>
>