public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/3719] New: stop propogation of Test*.*Internals Date: Thu, 14 Dec 2006 15:10:00 -0000 [thread overview] Message-ID: <20061214150950.3719.cagney@redhat.com> (raw) In the beginning there was a single standalone test program; and the coders felt that life was good. But then a second test was needed, and so the first test was copied and modified, this giving birth to a second standalone test program, and so again the coders felt that life was pretty good. But then things started to go wrong. The original test was copied again and again and again, this leading to many similar standlone test programs, each doing what they needed but each also duplicating much of work of the older tests. There was much confusing duplication within the source code, and much slowness of the testsuite run. There were rumblings, but on the whole, the coders still felt that life was good. But then the architect declared "Thou shall go forth and tests using JUnit." And all the coders celebrated, for they had been given a challenging task, and again they felt happy. But then a voice in the wilderness cried, "but what of those old tests", and the architect replied "thou shall refactor". And many tasks were refactored, and there was much use of JUnit, and coders celebrated and life seemed good. But unfortunatly a few tests remained. These were the oldest tests, that contained the most complex code, these were the tests that refused to change. But the coders kept refactoring, and the most complex code could see if nothing was done it too would soon be clensed of complexity and converted to JUnit. And so it hatched a plan. Late one morning, when all the coders were sleeping, the most complex code would slip into a coders office, create an Invisibility Internals class, and hide itself. That way, in the afternoon, when the coders awoke, they would find the complex code gone and assume that all was refactored and coding life could return to normal. And so the most complex code hatched its plan, and the coders were indeed fooled in to thinking all was refactored and things appeared to return to normal. But unfortunatly the most complex code, no longer pround and visible, and fed by programmers hiding the other complex code, festered under the Invisibility Internals class turning into evilly complex code. Things were most definitly not good. -- Summary: stop propogation of Test*.*Internals Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: cagney at redhat dot com OtherBugsDependingO 2234 nThis: http://sourceware.org/bugzilla/show_bug.cgi?id=3719 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2006-12-14 15:10 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-14 15:10 cagney at redhat dot com [this message] 2006-12-14 15:48 ` [Bug general/3719] " cagney at redhat dot com 2006-12-14 16:14 ` cagney at redhat dot com 2006-12-14 16:23 ` cagney at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20061214150950.3719.cagney@redhat.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).