summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Burrows <dburrows@debian.org>2010-07-10 15:28:24 -0700
committerDaniel Burrows <dburrows@debian.org>2010-07-10 15:28:24 -0700
commitbe5269d15f0e29b3683edc950767b099699e1df0 (patch)
treecb4cf3fe3d68cab3094ce02f713d8a3e7113a515
parent819c9845ec2651f8797b0d13f5ffd0d5d1df685e (diff)
downloadaptitude-be5269d15f0e29b3683edc950767b099699e1df0.tar.gz
Delete an obsolete comment that snuck into my earlier roll-up patch.
-rw-r--r--tests/test_cmdline_download_progress_display.cc11
1 files changed, 0 insertions, 11 deletions
diff --git a/tests/test_cmdline_download_progress_display.cc b/tests/test_cmdline_download_progress_display.cc
index 57b23de3..1f0d5310 100644
--- a/tests/test_cmdline_download_progress_display.cc
+++ b/tests/test_cmdline_download_progress_display.cc
@@ -260,17 +260,6 @@ TEST_P(CmdlineDownloadProgressDisplayTest, UpdateProgress2)
EXPECT_TRUE(progress->update_progress(status2));
}
-// The various file_started(), file_finished(), etc routines don't
-// exhaustively verify that the status is displayed correctly; the
-// assumption is that it gets displayed by the same routine that backs
-// update_progress(). I test a few different status values to
-// sanity-check this assumption, but that's all.
-//
-// (I could factor the actual display code into a separate routine
-// behind another interface, exhaustively test it in its own unit
-// test, and just verify here that the status is passed through when
-// expected. Probably not worth the trouble)
-
TEST_P(CmdlineDownloadProgressDisplayTest, FileStartedWithIdNoNameWithFileSize)
{
{