Bug 27991 - bugzilla_unitest.py needs to know how to run a local bugzilla instance
Summary: bugzilla_unitest.py needs to know how to run a local bugzilla instance
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 27977
  Show dependency treegraph
 
Reported: 2009-08-04 12:08 PDT by Eric Seidel (no email)
Modified: 2009-08-04 13:12 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2009-08-04 12:08:12 PDT
bugzilla_unitest.py needs to know how to run a local bugzilla instance

I've never set up bugzilla before. :)  But I do believe it should be possible for us to run a local instance from our python unit tests so that we can test the functions in bugzilla.py against a live instance.

I ran ./BugsSite/checksetup.pl once to learn that we'll need a whole bunch of perl modules installed on any machine that wants to run bugzilla. :(
Comment 1 Eric Seidel (no email) 2009-08-04 12:11:16 PDT
This doesn't block bug 27977, but is related.
Comment 2 David Kilzer (:ddkilzer) 2009-08-04 13:04:24 PDT
(In reply to comment #0)
> I ran ./BugsSite/checksetup.pl once to learn that we'll need a whole bunch of
> perl modules installed on any machine that wants to run bugzilla. :(

You also need a database (PostgreSQL, MySQL or Oracle).  Having bugs in the database would be handy as well, but you might be able to come up with a way to mirror a small subset of bugs from bugs.webkit.org with the WebServices API.
Comment 3 Eric Seidel (no email) 2009-08-04 13:12:41 PDT
We can easily dump some bugs into some fixture files though.  I bet it's possible to run mysql with some flat-file backends.  I had thought mysql came installed on mac os x, but I guess not.