Catchlist_todo

I've created an entity factory that allows the creation of tasks, projects, etc with simple functions, like so:

def create_task(auth_client, **kwargs):
    """Helper to create a task with custom properties"""
    payload = {
        "title": kwargs.get("title", "Sample Task"),
        "description": kwargs.get("description", ""),
        "status": kwargs.get("status", "open"),
    }

    with allure.step(f"Create task: {payload['title']}"):
        response = auth_client.post('/api/tasks', json=payload)
        assert response.status_code == 201, f"Failed to create task: {response.text}"
        task = response.json()

    return task


def create_project(auth_client, **kwargs):
    """Helper to create a project with custom properties"""
    payload = {
        "title": kwargs.get("title", "Test Project"),
        "description": kwargs.get("description", ""),
        "win_condition": kwargs.get("win_condition", ""),
        "reason": kwargs.get("reason", ""),
        "next_step": kwargs.get("next_step", ""),
    }

    with allure.step(f"Create project: {payload['title']}"):
        response = auth_client.post('/api/projects', json=payload)
        assert response.status_code == 201, f"Failed to create project: {response.text}"
        project = response.json()

    return project

This is the right way to create entities when the test just needs a thing to exist. Like if you just need a project to exist in order to attach a task to it, this is the right way to create that project.

It may actually be useful to create all entities like this, the use of kwargs lets you do whatever you want, and the function includes the boilerplate of checking for a 201 and such, so consider using it all over the place. Both to reduce boilerplate and to provide a single place to change test code if implementation changes.