High-priority areas of Tor have test coverage > 80%

We'd like the unit test coverage on the highest-priority areas of Tor to be very high indeed. This is a deliverable for October 2016.

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified points::parent priority::medium severity::normal sponsor::S-can status::new tor-tests-coverage tor-unit-tests type::defect labels

Trac:
Sponsor: SponsorS to SponsorS-must

Trac:
Status: new to accepted
Owner: N/A to nickm

Trac:
Keywords: N/A deleted, tor-tests-coverage added

Trac:
Points: large to 6

Trac:
Severity: N/A to Normal
Points: 6 to parent
Reviewer: N/A to N/A
Parent: N/A to #17289 (moved)

Trac:
Owner: nickm to N/A
Status: accepted to assigned

Put all unowned "assigned" tickets back into "new".

Trac:
Status: assigned to new

Trac:
Sponsor: SponsorS-must to SponsorS-can

Trac:
Keywords: N/A deleted, isaremoved added
Milestone: Tor: 0.2.9.x-final to Tor: 0.2.???

Unparenting.

Trac:
Parent: #17289 (moved) to N/A

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Keywords: isaremoved deleted, N/A added

Trac:
Keywords: tor-tests-coverage deleted, tor-tests-coverage tor-unit-tests added

moved to tpo/core/tor#17288 (closed)