Document the abstract models testing

[jocelyn@…]

Testing abstract models within reusable apps is easy, as explained here or ​here.

I think a hint in the doc titled ​advanced testing topic would be usefull, and you ?

[Tim Graham]

Sure, if you could submit a patch I'll be happy to review it.

[JocelynD]

Ok, working on it.

[JocelynD]

documentation edit proposal (master)

[Tim Graham]

This looks pretty good. A couple comments:

• There should be just 1 newline between sections of the docs.
• eg should be e.g.
• I suggest writing the link to the test database as :ref:`the test database <the-test-database>` so that "The" isn't capitalized in the generated text.
• It would be helpful to include an example of what a "stub child class" looks like as it may not be obvious to a reader.

Please uncheck "patch needs improvement" if you can make these improvements; thank-you!

[Marc Tamlyn]

This approach is basically a hack - it relies on the fact your tests file is not imported by the rest of the code. If there happened to be a utility function which some lazy developer wrote in the tests and then imported into main project code, this model would potentially become visible during other work. As such, I'm at least -0 on including this documentation, but in any case it should come with bigger warnings in the proposed patch.

[Tim Graham]

Closing per Marc's concerns.