Since we only care about the name, we don't need to bother with adding an "is published"
row: keep things minimal! Create a product Bar and another Foo1. Man, those dinos
can't wait to get a hold of such interesting product names!

I'll repeat this one more time for fun. you can find three things by
their text: links, buttons and fields. Use findLink(), findButton() and findField()
on the page or individual elements to drill down to find things. Add
assertNotNull($link, 'Could not find link '.$linkText); in case something
goes wrong. Finally click that link!

That's fine: I like to start lazy and assume everything is there. When I need the
steps to be more flexible, I'll add more code. Add an isset('is published') so
if it's set and equals yes, we'll publish it:

Add a new deleteAction() and a route of /admin/products/delete/{id}. Name
it product_delete. We could get fancy and add an @Method annotation that say
that this will only match POST or DELETE requests. Let's keep it simple for now:

To add the delete link, find list.html.twig and add a column called Actions. Since
you should POST to delete things, add a small form in each row, instead of a link
tag. Make the form point to the product_delete route and add method="POST". And
instead of having fields, it only needs a submit button whose text is "Delete".
Add some CSS classes to make it look nice - don't get too lazy on me:

It stops again, but no error this time: the delete button looks fine. Press enter
to keep this moving.

But it still fails! The test could not find a "Delete" link to click in the "Foo1"
row. The cause is subtle: links and buttons are not the same. We click links but
we press buttons. In the scenario I should say I press Delete instead of click: