[p2pu-dev] Current testing setup -- Lernanta

[Jos Flores]

A bit more digging into the current setup.

I cannot make any tests pass without passing in
FORCE_DB=whatever_value_you_want_here

Passing FORCE_DB nullifies the supposedly speed gains that test_utils
provide. So this library is actually creating a bunch of dependencies
(at least Jinja, but probably nose too) and providing no benefit
whatsoever... can anyone please correct me if I'm wrong?

cheers,
Jose



On 23 June 2012 23:01, Jos Flores <josmasflores at gmail.com> wrote:
> Hi guys,
>
> thinking about ways to improve test coverage overall, and wondering...
> how attached are we to the current testing setup?
>
> I know little about testing django apps, but I can see that test_utils
> kinda takes over the test runner.
> I see a bunch of DB tests, which are cool, but not what I was
> expecting to see. There are no unit tests (as in isolated tests) that
> I can find, and I'd like to target that first, and create tests with
> every bug fix I work on from now own.
>
> Not sure about nose either. So my main question (again) would be, how
> attached are we to test_utils and nose?
> It's quite possible the setup was inherited from batucada and no one
> knows very well what's going on. If that is the case, can you please
> let me know :)
>
> cheers,
> Jose