📢 New Blog Post: The Samurai’s Blade — A Story of Automation Testing

Hi everyone! :waving_hand:
I recently published a new blog post titled “The Samurai’s Blade: A Story of Automation Testing.”
It’s a creative take on explaining automation testing through a story format.
I’d really appreciate it if you could give it a quick read and share your thoughts or feedback! :blush:

:open_book: Read here: https://sasikiran-qa.blogspot.com/2025/11/the-samurais-blade-story-of-automation.html

Nice effort. Given the Japanese story, please checkout kanban as well.

Here’s some feedback:

  1. It would be nice to showcase task breakdown and assigning points to each task (eg. Fibonacci system).
  2. Do highlight the fact that points are relative and that it’s not a good idea to assign time / days to these points, unless historical data of similar task is encountered.
  3. Using a longer duration that fits a typical sprint duration of 2 weeks would be a lot more relatable to real projects.
  4. Since some of these constraints on the sword might be new to the team, the term spike would fit the story.
  5. When covering customer constraints, do mention BDD and acceptance tests.
1 Like

Better get your domain, so you’ve a personal identity.

1 Like