git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH (amend)] cvsserver: Add test cases for config file handling

From
Frank Lichtenheld <frank@lichtenheld.de>
Date
May 14, 2007, 12:59 UTC
Message-ID
<20070514125915.GB5272@planck.djpig.de>
In-Reply-To
<7vtzugqym8.fsf@assigned-by-dhcp.cox.net>
On Sun, May 13, 2007 at 01:04:15PM -0700, Junio C Hamano wrote:
Show 12 quoted lines
> Frank Lichtenheld <frank@lichtenheld.de> writes:
> 
> > Add a few test cases for the config file parsing
> > done by git-cvsserver.
> >
> > Signed-off-by: Frank Lichtenheld <frank@lichtenheld.de>
> > ---
> >  t/t9420-git-cvsserver-config.sh |  109 +++++++++++++++++++++++++++++++++++++++
> >  1 files changed, 109 insertions(+), 0 deletions(-)
> >  create mode 100755 t/t9420-git-cvsserver-config.sh
> 
> Do we really need a separate test script that does quite similar setup?
Right now, probably not.

But I certainly don't intend to do all the tests in one big file which will become rather large over time. If you're concerned with code duplication, maybe I should move the code to a separate file and source it from there?

Gruesse,
-- 
Frank Lichtenheld <frank@lichtenheld.de>
www: http://www.djpig.de/
Previous: Junio C HamanoNext: Frank Lichtenheld
Message 4 of 7 in “cvsserver: Add test cases for config file handling”
  1. cvsserver: Add test cases for config file handlingFrank Lichtenheld, May 13, 2007
  2. cvsserver: Add test cases for config file handlingFrank Lichtenheld, May 13, 2007
  3. Junio C HamanoMay 13, 2007
  4. Frank LichtenheldMay 14, 2007
  5. Frank LichtenheldMay 19, 2007
  6. Junio C HamanoMay 19, 2007
  7. Frank LichtenheldMay 19, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.