Hi Koen,

I've read the blog post and enjoyed it. Here are a couple of comments:

- The step definition pragma is like: <heraStepDefinition: #(Given 'I have credentials to sign in')>
Why didn't you use a keyworded selector like: <heraStep: #Given definition: 'I have credentials to sign in'>

- What happens if a step method is empty, i.e. it was generated from Gherkin, but not modified by the developer? In Pharo an empty test method passes. I dislike it. I think any test method without assertions should fail. This change will break smoke tests. So, we need to introduce an assertion message or a pragma dedicated to smoke tests.

Best,
Noury
On Sun, Mar 9, 2025 at 2:37���PM Koen De Hondt <koen@all-objects-all-the-time.st> wrote:
Dear Pharo users and developers,

In my series of blog posts on testing, I published a new post on tools for running Gherkin-style test scenarios in Pharo. See��https://all-objects-all-the-time.st/#/blog/posts/13. It is an introduction. Future posts will dig into the details.

As always, all feedback is welcome.

Happy reading!

Ciao,
Koen



--
Noury Bouraqadi