Move majority of e2e tests from API Fuzzing to DAST API

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem

The majority of the e2e tests jobs are API Fuzzing jobs as API Fuzzing mode pre-dates DAST API. API Fuzzing runs are not deterministic and often result in status code issues or response analysis with INTERNAL SERVER ERROR messages. This makes the tests flaky and not great judges of code quality.

Proposal

Goal: Better signals on code quality, fewer flaky or unreliable tests.

• Move most of the e2e tests to DAST API mode.
  • DAST API mode is more deterministic and reliable, a perfect match for our E2E tests.
• Consider adding some fuzzing specific issues into the target image with a goal of making them reliable
  • Faulting on string values that grow
  • Faulting on numerical edge cases with some +/- range