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

Re: tests for git-p4

From
Simon Hausmann <simon@lst.de>
Date
Jul 13, 2008, 12:26 UTC
Message-ID
<200807131426.09688.simon@lst.de>
In-Reply-To
<e48c5e540807120524rabdcfa6vd91c16ef1b0f80a0@mail.gmail.com>
On Saturday 12 July 2008 14:24:10 Matt McClure wrote:
Show 12 quoted lines
> I'm planning to write a "p4-fast-export" that will facilitate using
> Bazaar on projects maintained in Perforce.  I'd like to reuse code
> from git-p4 since it appears to have much of the functionality I want.
>  In fact, the main reason I can't just use git-p4 today is that it
> does too much: it pushes the Perforce fast-export representation
> directly into Git.  I'm going to work on covering the existing
> functionality in tests before I start modifying the code, and I could
> try to write those tests such that they'll be useful to the Git
> project as well.
>
> Would my tests be of interest to git-p4's authors?  Is there any
> existing test framework for git-p4 that I missed?

There are currently no automated tests for git-p4. I would certainly be interested, but I forsee difficulties testing the interaction with p4 in a general way independent from a specific server setup.

Simon
Previous: Johannes SchindelinNext: Matt McClure
Message 3 of 4 in “tests for git-p4”
  1. Matt McClureJul 12, 2008
  2. Johannes SchindelinJul 12, 2008
  3. Simon HausmannJul 13, 2008
  4. Matt McClureJul 13, 2008

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.