<!-- The first three sections: "Problem to solve", "Intended users" and "Proposal", are strongly recommended, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Problem to solve Fuzz testing provides lots of valuable information to users in terms of ways to crash the app. Currently, it is difficult for them to access this information since it is buried in individual pipeline results, rather than in other screens they regularly interact with, such as the Merge Request widget. ### Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test) ### Further details ### Design 1 - MR Widget bar + expanded info (In scope if https://gitlab.com/gitlab-org/gitlab/-/issues/12896 is NOT done) **When implement it in an old MR widget** | Old MR widget collapsed | Old MR widget expanded | | ------------------ | ----------- | | https://www.figma.com/file/ckuKpzAUe7M0iAF9NdnDQl/Fuzz-testing-MR-page?node-id=4%3A0 |https://www.figma.com/file/ckuKpzAUe7M0iAF9NdnDQl/Fuzz-testing-MR-page?node-id=1%3A2| | We contribute the number if we can tell the findings are new or not | Download artefacts available from this page, rest is the same as other scanners | ||| ### Design 2 - MR Widget bar (In scope if https://gitlab.com/gitlab-org/gitlab/-/issues/12896 is done) **When implement it in a one new MR widget** | New MR widget collapsed | New MR widget leads to a new tab | | ------------------ | ----------- | |https://www.figma.com/file/ckuKpzAUe7M0iAF9NdnDQl/Fuzz-testing-MR-page?node-id=3%3A142| https://www.figma.com/file/ckuKpzAUe7M0iAF9NdnDQl/Fuzz-testing-MR-page?node-id=3%3A1236| | We contribute the number if we can tell the findings are new or not| | |  | | ### Design 3 - Finding Modal (Definetely in scope) **No matter old or new MR widget, the modal window details keep the same** | Coverage guide - collapsed | Coverage guide - expanded | | ------------------ | ----------- | | https://www.figma.com/file/ckuKpzAUe7M0iAF9NdnDQl/Fuzz-testing-MR-page?node-id=4%3A2 |https://www.figma.com/file/ckuKpzAUe7M0iAF9NdnDQl/Fuzz-testing-MR-page?node-id=78%3A1092| | |https://www.figma.com/file/ckuKpzAUe7M0iAF9NdnDQl/Fuzz-testing-MR-page?node-id=80%3A0 | | we only show 6 lines of stack trace | we only keep one scroll bar of the modal window | |  |   | - :movie_camera: Video walkthrough: https://youtu.be/rKX1MJsHFCo ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html * Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements * If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html --> ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> Add usage ping to record the number of times users view the fuzz testing results. ### What is the type of buyer? <!-- What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/ In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Is this a cross-stage feature? <!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group&#39;s broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> ### Links / references ### Implementation Strategy #### Frontend | Tasks # | Description | ~frontend issue | ~frontend weight | | ----------- | -------------------------------------------------------------- | ---------------------------------------------------- | ---------------------- | | 1 | Fuzz testing results in MR widget - Coverage guided fuzz testing - Update getters to reflect updated summary counts| https://gitlab.com/gitlab-org/gitlab/-/issues/254637 | ~"frontend-weight::2" | | 2 | Fuzz testing results in MR widget - Coverage guided fuzz testing - Render fuzzing report section in MR widget| https://gitlab.com/gitlab-org/gitlab/-/issues/251017 | ~"frontend-weight::2" | | 3 | Fuzz testing results in MR widget - Coverage guided fuzz testing - Render fuzz related vuln data in modal| https://gitlab.com/gitlab-org/gitlab/-/issues/254650 | ~"frontend-weight::3" | | 4 | Fuzz testing results in MR widget - Coverage guided fuzz testing - Add artifact download dropdown| https://gitlab.com/gitlab-org/gitlab/-/issues/254711 | ~"frontend-weight::3" | | 5 | Fuzz testing results in MR widget - Coverage guided fuzz testing - Docs| https://gitlab.com/gitlab-org/gitlab/-/issues/254652 | ~"frontend-weight::2" | ## Follow-up Frontend Remove Feature Flag - https://gitlab.com/gitlab-org/gitlab/-/issues/257839 #### Backend | Tasks # | Description | ~backend issue | ~backend weight | | ----------- | -------------------------------------------------------------- | ---------------------------------------------------- | ---------------------- | | 1 | Fuzz testing results in MR widget - Coverage guided fuzz testing - Implement coverage fuzzing report endpoint for Mr widget | https://gitlab.com/gitlab-org/gitlab/-/issues/255169 | TBD |