Skip to content

Add real Django backend test instance for e2e and fuzzing tests #2422

@arkid15r

Description

@arkid15r

Is your feature request related to a problem? Please describe.

Our current testing setup relies on mocked data and doesn’t use a live backend. To strengthen test reliability and enable full-stack and fuzzing tests, we need a real Django backend test instance that can run in an isolated environment for both local and CI/CD workflows.

Describe the solution you'd like

  • Provide a real backend instance for use in integration, end-to-end, and fuzzing tests.

  • Ensure the setup works consistently across local development and CI/CD.

  • Keep the test environment isolated from development and production data (consider separate fixture vs existing nest.json.gz data)

  • Developers can run tests against a real backend environment with minimal setup.

  • CI/CD pipelines can automatically launch and use the backend for full-stack tests.

  • Documentation clearly explains how to use the new test environment.

  • The same setup can be extended for future test types and automation.

Are you going to work on implementing this?

  • Yes
  • No

Additional context

This will lay the groundwork for more comprehensive testing within OWASP Nest, including fuzzing and real backend interaction scenarios, improving the accuracy and confidence of test results.

Metadata

Metadata

Assignees

Type

No type

Projects

Status

In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions