On Thursday, 20 February 2014 00:35:43 UTC+5:30, Andrew Pashkin wrote:
>
> 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
On Thursday, 20 February 2014 00:35:43 UTC+5:30, Andrew Pashkin wrote:
>
> 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
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
I just finished reading the unittest documentation. I'll start with the
Django testing code ( the definitions for SimpleTestCase,
TransactionTestCase, TestCase, etc.) tomorrow. Any feedback at this time,
would be quite encouraging. Even a -0 or a -1 would tell me if I need
suitable course
Hi,
On Saturday, 15 February 2014 06:42:49 UTC+5:30, Russell Keith-Magee wrote:
>
> Hi Akshay,
>
>>
> Great to hear! Here's some feedback:
>
>
>> One of the improvements I see is classification of test cases.
>> Classifying them into categories (read multiple-categories), would make it
>>
On Saturday, 15 February 2014 20:47:37 UTC+5:30, Chris Wilson wrote:
>
> Hi all,
>
> It just occurred to me that most classification systems are completely
> arbitrary and therefore not very useful. What's a "system" test and how
> would I know whether I need to run it?
>
For development
On Sunday, 16 February 2014 06:27:01 UTC+5:30, Josh Smeaton wrote:
>
> Just a few observations that I've had when running the test suite that may
> be relevant.
>
> - There are lots and lots of different test modules that may be relevant
> to a particular change, and some may not seem relevant
I'm so sorry. Was busy with some assignments. I will look into all the
mentioned points and reply back as soon as possible. :)
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from
Just a few observations that I've had when running the test suite that may
be relevant.
- There are lots and lots of different test modules that may be relevant to
a particular change, and some may not seem relevant until you run the
entire suite
- bug* modules are hard to classify without
Hi all,
On Sat, 15 Feb 2014, Russell Keith-Magee wrote:
One of the improvements I see is classification of test cases.
Classifying them into categories (read multiple-categories), would make
it easier for users/developers/maintainers to run them. Basis of
classification,etc is what I am
Hi Akshay,
On Fri, Feb 14, 2014 at 9:12 PM, Akshay Jaggi <akshay1994@gmail.com>wrote:
> Hello!
> I was planning to work on improving the Test-Suite for GSOC 2014.
> I would need some help in formalising and improving my proposal, so that
> it meets the requirements.
>
Hello!
I was planning to work on improving the Test-Suite for GSOC 2014.
I would need some help in formalising and improving my proposal, so that it
meets the requirements.
One of the improvements I see is classification of test cases. Classifying
them into categories (read multiple-categories
12 matches
Mail list logo
