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

Re: [EGIT PATCH 7/7] Create an automatic UI test for the Git Import Wizard

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jan 12, 2009, 16:45 UTC
Message-ID
<20090112164514.GG10179@spearce.org>
In-Reply-To
<200901081957.20591.robin.rosenberg.lists@dewire.com>
Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
> 
> We could hold onto this patch. It might be better if we start the built in git daemon and clone
> from it, or from file, instread of jgit.org, but please try it out and see if it looks like a good a approach to
> use SWTBot for UI tests.
I'm not applying this patch for two reasons:
1) I spent 30 minutes trying to get SWTBot installed and running,
I gave up.  It doesn't want to run in my Eclipse.  Heck, I didn't
even get as far as running, I couldn't get it to install far enough
to get the project to compile.
2) I really want to avoid remote network access during JUnit tests.
Now that we have our own server process we can run it over a pipe
or something to do this test.  Or at worst, bind to a random port
on the loopback and have the client clone from that port.
-- 
Shawn.
Previous: Robin Rosenberg
Message 11 of 11 in “Import Wizard cleanup fixes and test”
  1. 0/7 Import Wizard cleanup fixes and testRobin Rosenberg, Jan 8, 2009
  2. 1/7 Create the import wizard question checkbox properlyRobin Rosenberg, Jan 8, 2009
  3. 2/7 Fix two strings in the cloning wizard that were not translated.Robin Rosenberg, Jan 8, 2009
  4. 3/7 Add shortcuts to the Git cloning wizardRobin Rosenberg, Jan 8, 2009
  5. 4/7 Normalize paths to /-format when parsing GIT URI'sRobin Rosenberg, Jan 8, 2009
  6. 5/7 Add UNC test case to URIish testRobin Rosenberg, Jan 8, 2009
  7. 6/7 Treat null scheme as file: in git import wizardRobin Rosenberg, Jan 8, 2009
  8. 7/7 Create an automatic UI test for the Git Import WizardRobin Rosenberg, Jan 8, 2009
  9. Robin RosenbergJan 8, 2009
  10. Robin RosenbergJan 8, 2009
  11. Shawn O. PearceJan 12, 2009

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.