ubuntu-accomplishments-contributors team mailing list archive

[Matt Fischer <matthew.fischer@xxxxxxxxxxxxx>]

On 07/23/2012 10:09 AM, Jono Bacon wrote:
> On Fri, Jul 13, 2012 at 7:21 PM, Matt Fischer
> <matthew.fischer@xxxxxxxxxxxxx> wrote:
> > I have pushed up a fix along with some other unit test changes, but Cielak
> > or Jono, please test it and maybe wait until I'm around (Monday?) to merge
> > it?
> How do I test this? 'quickly test' is working for me.
>
>      Jono

I assume you meant "not working".  I'll work with you on IRC about that 
since it works for me.  For future reference for everyone else:

You can run the tests 3 ways:

1) *python ./tests.py*

mfisch@caprica:~/experiments/accomps/accomplishments-daemon/u4/accomplishments/daemon/tests$ 
python ./tests.py
------------------- Ubuntu Accomplishments Daemon - 2012-07-23 
10:16:39.439757 -------------------
<snip>
----------------------------------------------------------------------
Ran 21 tests in 0.107s

OK (skipped=3)



2) *quickly test*

mfisch@caprica:~/experiments/accomps/accomplishments-daemon/u4$ quickly test
.S...............SS..
----------------------------------------------------------------------
Ran 21 tests in 0.325s

OK (SKIP=3)


3)*by building the package with dpkg-buildpackage

*Building the package ising a pbuilder environment is the safest bet 
here since it more correctly emulates what the build machine environment 
is.  For example, the build server won't have any locales, that's why we 
generate ours in the test hook in debian/rules.