Another advantage of Pytest is its ability to launch tests written in
all styles - PyUnit, Nose, and Pytest own style.
Recently I understood that it is a good practice to launch tests not
only for project, but for all packages it uses before deployment - to
ensure that nothing is broken (like mi
will be useful.
On Sun, 6 Apr 2014, Andrew Pashkin wrote:
Some Pytest advocacy:
1) Pytest has convenient tests collection options - you can just
specify folder to run all tests in it. It is also possible to
filter tests by regex, and select specific ones.
I do use pytest and it has a lot of
Some Pytest advocacy:
1) Pytest has convenient tests collection options - you can just specify
folder to run all tests in it. It is also possible to filter tests by
regex, and select specific ones.
2) PyUnit:
class MyTestCase(TestCase):
def test_something(self):
expected_content = ..
Proof of concept for pymorphy solution:
https://gist.github.com/StillNewb/9703843
On Saturday, March 15, 2014 9:20:24 PM UTC+4, Алексей Сидаш wrote:
>
> Hello
>
> Yes, Adam Mesha seems to be right. The problem of translation is very
> complicated.
> I see only one solution, all the text in admin
The problem is actually exists, I also want to find a way, how to rid my
cleints of that crazy wording in admin-site.
I've found promising package - pymorphy2
(https://github.com/kmike/pymorphy2), it can find grammatical information
for words and translate words to needed forms. So all what is n
>
>
>>1. Distributed testing (speed up, especially on multi-core machines),
>>Line Coverage, etc using plugins
>>
>> How would this work? We still have shared resources like the database
> where you can't just run 10 Test against in parallel.
>
There is django plugin for py.test
Ive made workaround for this case as external
app<https://bitbucket.org/andrew_pashkin/django-deep-prefetch>
.
On Sunday, February 9, 2014 12:14:32 AM UTC+4, Andrew Pashkin wrote:
>
> With GenericForeignKey functionality, it is possible to refer to
> arbitrary model. Let's a
BTW - I recent;y trid to run Django test suite with Py.test and
pytest-django plugin and achived some success - main problem, that some
tests are failing and reason of it is not clear to me yet.
This solution require pytest, django-pytest packages and lightweight
configuration.
See patch in atta
Got this while tried to laucnh Djangos test suite on
fb1e3435a4d7e0265f19a1a9f130c9485fb8dfe9
On Tuesday, October 15, 2013 4:56:56 PM UTC+4, rok wrote:
>
> I have recently been testing the 1.6b4 tag with a new app we are writing,
> using apache and wsgi. However, I could not get rid of the follo