Hi everyone- this is going to be a quick demo of the corpus management page. um This is a high fidelity mock because we do not have the back end ready at this time. So these are the original designs that we have here. So I'm going to hop over to the configuration page so right now we do not. We still don't show the link over the corpus management page just because we're not surfacing it to the users yet, but I will go ahead and demo the mocked out or high fidelity mock of corpus management.

So we do have the loading spinner show up. um The fetch is mocked out and the way we have the setup is to allow for either rest or graphql endpoints, so using one or the other or both should not be too difficult.

The data that's populated here is all marked out data, but the data is based off of existing jobs, so they work. So if you click on latest job, it will open up a fuzzing job that is actually one from the security reports project that we have. I believe it's public, so for the purposes of demoing to the user, um they should link correctly.

um I did try to cover all the ui states that were covered in the design, so we handle all those edge cases when we do have the back end ready. So we have target here not set for these um latest job not available.

Last updated. Last used uh download does actually download a corpus artifact here, so we click on that. We can see uh the coverage report. I guess this is a coverage fuzzing job. So if we do have the correct job uh running and generating the right artifact download, then we should be okay. um This is just for the purposes of the demo.

um The delete works as well. You click on this. You get this confirmation uh modal, you click delete and it is removed from the table. I'll do another one, just as it happened kind of quickly so now they disappear and the counts do update as well as you're deleting these and uh yeah that's pretty much it um new corpus button right now um we'll be mocking that out um in this coming milestone. So for now there's a placeholder. You click on this you'll see just the browser alert but we'll well.

But what will happen in the uh follow-up milestone? We will implement a mocked out version of the corpus upload so we'll be able to simulate uh file uploads.

The link here learn more right now links to the existing coverage fuzzing uh docs, but once we have the actual uh documentation implemented for corvus management, we could just link right to that and that's just as simple as updating the path so yeah. This is a I guess uh as far as like I've gotten with the demo. um Hopefully it was.

Productive.