Wow how cool is this that we can use normal email for review
correspondence?

There's no reason to run the tests against the quickstart database, I'm
sorry you'll have to update your scripts.  We want run set of tests that
run against travis and internal test harness, sticking with the dba/dba
cloud/user conventions will make that simpler.

Yes the internal bamboo builds will run against a fake NuoDB instance and
travis will run against an installed product, but I don't see how or why
that's relevant.   Certainly its a good thing to cover both cases!

On Wed, Nov 13, 2013 at 9:02 AM, thebithead <notifications@github.com>wrote:

> In tests/testdb.inc:
>
> > @@ -1,11 +1,16 @@
> >  <?php /* $Id: testdb.inc 161049 2012-03-26 01:37:06Z tgates $ */
> >
> > -$user = 'cloud';
> > -$password = 'user';
> > +$user = 'dba';
>
> Ok, but that does not match the username/password that external customers
> will have (default: dba/goalie, cloud/user), which is what my personal
> scripts are using.
>
> About the internal tests that use dba/dba, is that running from a NuoDB
> build tree, or an installed version of NuoDB? When we integrate the NuoDB
> PHP PDO Driver tests, we may want to test against an installed instance of
> NuoDB, not a devo instance.
>
> Also, is there a reason why all tests must be run against the DBA
> credentials instead of normal, unprivileged credentials? Certainly most of
> the tests won't require DBA credentials.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/nuodb/nuodb-php-pdo/pull/6/files#r7626047>
> .
>