Is it possible to work with Django's TestCase classes?

[reorx]

First, thank you for creating this amazing tool; it's already proving useful for my Node.js project. However, my primary job involves working with several Django projects, all of which use Django's built-in test mechanism, specifically the TestCase class, which is a subclass of unittest.TestCase. I'm wondering how to make tdd-guard work with these projects without migrating them to pytest, which is nearly impossible due to the extensive historical code that would be difficult to change.

[nizos]

Hi @reorx!

Thank you for the kind feedback! I'm really happy it's working well for your Node.js project!

I haven't tried using it with the setup you described but I'll look into adding support to make sure it works for Django's test framework. I should be able to get this done within a weekend or two (unless someone beats me to it!).

Thanks for bringing this up! :)

[reorx]

Glad to know it's in the plan, but there's no need to hurry, take your time, we all know that working on open-source projects is not easy!

If you don't mind, I'd like to briefly introduce my setup of organizing tests in Django for your reference. It's quite simple, just like how I do in jest. The file structure is like this:

breeze_web/
├── tests
│   ├── __init__.py
│   ├── test_posts_views.py
│   ├── test_settings_schemas.py

breeze_web is the Django project, tests is the folder to put test files.

Each test file have one single class that inherits django.test.TestCase (like describe() in jest), with many methods to actually test the logic (like test() in jest). Take test_posts_views.py for example:

from django.test import TestCase

class PostsViewTestCase(TestCase):
    """Test cases for posts view"""

    def setUp(self):
        ...

    def test_posts_view_requires_authentication(self):
        ...

    def test_posts_view_basic_functionality(self):
        ...

    def test_posts_view_filter_by_category(self):
        ...

My problem when using Claude Code is that, when implement a new feature, CC like to write all the code of different levels (pure functions, database operations, business logics, HTTP views), then write all the tests needed for the new code, which means creating several test files and dozens of test methods. But what I want is that when CC completes a small part of the whole plan that is enough to write a unit test, it writes the test and ensure it passes. then go on to the next task. Ideally one test method a time, but even one TestCase a time would make my life much easier.

Hope my example and thoughts would help on adding the support to Django test.