This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/14233] New: Many of tst-*.c lack any description of the assertions they test
- From: "bugdal at aerifal dot cx" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Thu, 14 Jun 2012 00:22:53 +0000
- Subject: [Bug libc/14233] New: Many of tst-*.c lack any description of the assertions they test
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14233
Bug #: 14233
Summary: Many of tst-*.c lack any description of the assertions
they test
Product: glibc
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: libc
AssignedTo: unassigned@sourceware.org
ReportedBy: bugdal@aerifal.cx
CC: drepper.fsp@gmail.com
Classification: Unclassified
Browsing some of the tst-*.c files in glibc, I noticed that many lack any
comments about what requirement they're testing for. I'm not sure if this is a
"bug" strictly speaking, but it seems problematic in that:
1. It's difficult to audit/debug them and determine if they're actually testing
for what they were intended to test. This is especially problematic for tests
that involve (either as the subject of the test or as a side-difficulty of
testing) race conditions, where it may not be at all obvious where the races
are.
2. If a change introduces a bug, it may be hard to determine the cause without
reverse engineering the test to see what it was testing.
3. It would be nice to know if tests are asserting behavior required by the
standards, behavior required as part of the documented or unofficial
specification of glibc, undocumented behavior that known applications expect,
and/or quality of implementation issues.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.