馃帹 Design: API fuzzing: project level manage profiles

Background

Based on the discovery on the previous issue, we have two personas and many tasks. And the design becomes too big to cover within one issue. So I divided the original issue into 6:

  1. 馃帹 Design: API fuzzing: project-level configure with local(project) profile #330481 (closed)
  2. 馃帹 Design: API fuzzing: project level configure: edit beaver token #331500
  3. 馃帹 Design: API fuzzing: project level configure edit route #331498
  4. (This issue) 馃帹 Design: API fuzzing: project-level manage profiles #330496 (closed)
  5. 馃帹 Design: API fuzzing: project-level configure with group profile #330480
  6. 馃帹 Design: API fuzzing: group-level manage group profile #330482

Issue number 2 and 3 will need some help of research with issue-Problem validation: How people use group-level settings and project-level settings for API fuzzing

JTBD

When I am configuring a CI/CD security scan, I want to specify which assets need to be scanned and under which circumstances, So that I can ensure my assets are secure prior to or at their release.

Target Persona

This user is focusing on the personas:

those who use group-level profiles

Scenario

This issue is focused on the following scenario:

  • As a person who is responsible for API fuzz testing (works on project level), some times, I go look into profiles, to see which profiles use the most, perform the best, which ones are not. I might edit some profiles, remove the unused ones or create new ones. So that I have a better overview of the API fuzzing status for my project

Tasks

  • Scenario 1:
    • task 1: I want to have an overview of the status of all profile
    • task 2: I want to identify the good/bad ones
    • task 3: I want to edit some profiles
    • task 4: I want to remove some profiles
    • task 5: I want to create new profiles

Design proposal

overview-manage-profiles

Edited by Camellia X Yang