Mailing List Archive: Development and testing procedure

Development and testing procedure

Jun 8, 2011, 10:22 AM

Post #1 of 3 (3056 views)

Hi,

I've recently started to work on a few bug fixes, and am also looking at
making some improvements to `find_or_create_alternate`. As part of
this, I need to better understand how to test Bricolage in a development
environment.

I have read the entire Bric::Hacker section, and have contributed a few
minor bug fixes with the help of "Contributing a Bug Fix". However, I
am not clear on the best approach for running tests during the
development process.

I have found `inst/runtests.pl`, but it is failing to connect to the
database. Is there an installation process that I need to run to setup
a test database?

I have ended up running `make dist` and reinstalling Bricolage each time
I want to run the tests, which is okay for a final test, but not really
very efficient for testing as I go.

Is there a standard procedure that Bric hackers go through when
developing and bug fixing?

Regards,

Mike

Re: Development and testing procedure [ In reply to ]

greg at node79

Jun 8, 2011, 10:51 AM

Post #2 of 3 (2927 views)

Permalink

On 2011-06-08, at 1:22 PM, Mike Raynham wrote:

> Is there a standard procedure that Bric hackers go through when developing and bug fixing?

There's a little more detail in the "Testing" section of this wiki page:
https://github.com/bricoleurs/bricolage/wiki/coding-standards

I set up my Bricolage installation with "make dev" which makes symlinks rather than copies of files. So /usr/local/bricolage/lib actually points to the lib directory of my local Git checkout, which is handy. Other than that, it acts as a regular "make install" would (including setting up the database).

After some code changes, "make test" runs the regular test suite. "make devtest" will run all over the database and overwrite things, but I run that only on my throwaway "development" installation.

HTH,
--Greg

Re: Development and testing procedure [ In reply to ]

catalyst at mikeraynham

Jun 8, 2011, 3:10 PM

Post #3 of 3 (2920 views)

Permalink

On 8 Jun 2011 18:51, "Greg Heo" <greg@node79.com> wrote:
>
> On 2011-06-08, at 1:22 PM, Mike Raynham wrote:
>
> > Is there a standard procedure that Bric hackers go through when
developing and bug fixing?
>
> There's a little more detail in the "Testing" section of this wiki page:
> https://github.com/bricoleurs/bricolage/wiki/coding-standards
>
> I set up my Bricolage installation with "make dev" which makes symlinks
rather than copies of files. So /usr/local/bricolage/lib actually points to
the lib directory of my local Git checkout, which is handy. Other than that,
it acts as a regular "make install" would (including setting up the
database).

That's very cool, and just what I needed.

>
> After some code changes, "make test" runs the regular test suite. "make
devtest" will run all over the database and overwrite things, but I run that
only on my throwaway "development" installation.

Great, thanks. I'll dive in a little deeper when I get chance, and start
hacking away properly.

>
> HTH,
> --Greg
>

Regards,

Mike