Context:

• I am developing a standalone Django package that is intended to be added to existing Django projects.
• This package includes Django models with methods that interact directly with a database.
• I want to write tests for these methods using pytest and pytest-django.
• I need to run these tests in a CI/CD environment, specifically using GitHub Actions.

Problems Encountered:

1. Database Setup:

   • Since this is a standalone package, it does not include a manage.py file.
   • This makes it challenging to run typical Django management commands like migrate to set up the database schema for testing.

2. Table Creation:

   • I encounter errors indicating that the table for my model does not exist because the necessary migrations are not applied.
   • This is problematic because my tests need to interact with the database tables directly.

3. Fixtures and Setup:

   • I need to ensure the database tables are created and populated with initial data before the tests run.
   • My attempts to use pytest fixtures and manually create database tables within the tests have not been successful.

What I’ve Tried:

• Using pytest fixtures to set up the initial database state.
• Manually creating database tables within the test setup using direct SQL execution.
• Using the mixer library to populate the database with test data.

Desired Outcome:

• A reliable method to ensure the necessary database tables for my models are created before running the tests.
• Proper setup and teardown of test data within the standalone package.
• Integration with CI/CD pipelines like GitHub Actions without relying on manage.py commands.

Additional Information:

• I am using an in-memory SQLite database for faster test execution.
• The test environment should be isolated and not rely on external databases or services.

I am looking for guidance on how to approach this problem or best practices for testing Django models in a standalone package using pytest and pytest-django. Any advice or solutions would be greatly appreciated.