Opened 12 years ago

Closed 5 years ago

#4434 closed Bugs (fixed)

BOOST_AUTO_EST_CASE typos in docs

Reported by: Jonathan Wakely <jwakely.boost@…> Owned by: Raffi Enficiaud
Milestone: Boost 1.59.0 Component: test
Version: Boost 1.55.0 Severity: Cosmetic
Keywords: Cc:

Description

http://www.boost.org/doc/libs/1_43_0/libs/test/doc/html/tutorials/new-year-resolution.html repeatedly shows BOOST_AUTO_EST_CASE in the examples, should be BOOST_AUTO_TEST_CASE

Change History (9)

comment:1 by anonymous, 12 years ago

Component: Documentation → test
Owner: changed from Matias Capeletto to Gennadiy Rozental

comment:2 by Gennadiy Rozental, 11 years ago

Resolution: → fixed
Status: new → closed

fixed in a trunk. Expect to appear in next Boost Release

comment:3 by anonymous, 9 years ago

Resolution: fixed
Status: closed → reopened
Version: Boost 1.43.0 → Boost 1.55.0

Bug still exists: http://www.boost.org/doc/libs/1_55_0/libs/test/doc/html/tutorials/new-year-resolution.html

comment:4 by Raffi Enficiaud, 9 years ago

Owner: changed from Gennadiy Rozental to Raffi Enficiaud
Status: reopened → new

Fixed in branch feature/quickbookdoc

comment:5 by Raffi Enficiaud, 9 years ago

Status: new → assigned

comment:6 by Raffi Enficiaud, 7 years ago

Milestone: Boost 1.44.0 → Boost 1.59.0
Resolution: → fixed
Status: assigned → closed

comment:7 by madhur4127, 5 years ago

Resolution: fixed
Status: closed → reopened

This is not fixed and the typo is still in the documentation:http://www.boost.org/doc/libs/1_55_0/libs/test/doc/html/tutorials/new-year-resolution.html

comment:8 by anonymous, 5 years ago

But it's fixed in the current releases. Docs from old releases don't get fixed, because the release has already happened and Boost devs don't have time machines.

See http://www.boost.org/doc/libs/1_66_0/libs/test/doc/html/boost_test/practical_usage_recommendations/tutorials/bt_and_tdd.html

comment:9 by Raffi Enficiaud, 5 years ago

Resolution: → fixed
Status: reopened → closed

Yes, and the documentation you referred to is the one of 1.55 and it will stay like this forever. Fixed in 1.59 as it is mentioned in the ticket.

Note: See TracTickets for help on using tickets.