Re: Problem running test on bloodhound_dashboard

[Ryan Ollos <ry...@wandisco.com>]

On Thu, Jan 30, 2014 at 6:26 PM, Saint Germain <sa...@gmail.com> wrote:

> Hello,
>
> I've tried running the tests on bloodhound_dashboard and I have some
> trouble.
>
> It seems that it's missing a test_suite in bhdashboard/tests/__init__.py
>
> [...]
>
> Am I missing something or should I run the tests differently for the
> dashboard ?
>

I get the same result. I can't immediately figure out how to fix it, and I
really don't have a desire to dig into that code since it is likely going
away, so I think we should let Olemis fix it - it was all written by him
IIUC.

I pushed a few small fixes just now anyway, so that we can execute the unit
tests in the typical way:
PYTHONPATH=. python -m bhdashboard.tests.widgets.timeline
PYTHONPATH=. python -m bhdashboard.tests.widgets.__init__

We would like to have a consistent approach to unit and functional testing,
and the structure of the tests in bhdashboard and dependency on dutest
don't fit with approaches taken elsewhere. This has previously been
discussed:
http://markmail.org/message/f7zspmnh7tb64wf4

Besides that, the comments are not correct, there are references to Trac
0.11.x, and a dependency on TracXMLRPC that does't seem to be necessary. It
looks like the code was copied from a trac-hacks plugin, and care wasn't
taken to update it.

Re: Problem running test on bloodhound_dashboard

[Olemis Lang <ol...@gmail.com>]

On Sun, Feb 2, 2014 at 7:03 AM, Ryan Ollos <ry...@wandisco.com> wrote:

> On Thu, Jan 30, 2014 at 6:26 PM, Saint Germain <sa...@gmail.com> wrote:
>
> > Hello,
> >
> > I've tried running the tests on bloodhound_dashboard and I have some
> > trouble.
> >
> > It seems that it's missing a test_suite in bhdashboard/tests/__init__.py
> >
> > [...]
> >
> > Am I missing something or should I run the tests differently for the
> > dashboard ?
> >
>
> I get the same result. I can't immediately figure out how to fix it, and I
> really don't have a desire to dig into that code since it is likely going
> away, so I think we should let Olemis fix it - it was all written by him
> IIUC.
>
> I pushed a few small fixes just now anyway, so that we can execute the unit
> tests in the typical way:
> PYTHONPATH=. python -m bhdashboard.tests.widgets.timeline
> PYTHONPATH=. python -m bhdashboard.tests.widgets.__init__
>
> We would like to have a consistent approach to unit and functional testing,
> and the structure of the tests in bhdashboard and dependency on dutest
> don't fit with approaches taken elsewhere. This has previously been
> discussed:
> http://markmail.org/message/f7zspmnh7tb64wf4
>
> Besides that, the comments are not correct, there are references to Trac
> 0.11.x, and a dependency on TracXMLRPC that does't seem to be necessary. It
> looks like the code was copied from a trac-hacks plugin, and care wasn't
> taken to update it.
>

I'll take a look into this , but afaicr this happened looong time ago .

-- 
Regards,

Olemis - @olemislc

Apache(tm) Bloodhound contributor
http://issues.apache.org/bloodhound
http://blood-hound.net

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article: