1. It seems to take something that's already pretty straightfoward (RSpec) and just adds a couple keywords.
2. You're writing code when you should be describing features. Trying to remember where to put an underscore or what should be a symbol makes it harder to focus on describing the feature.
3. It greek to any non-developer. If you tried e-mailing this to a product owner or a user they would ask why you're sending code samples.
I know you addressed #3 in your blog post but why did you decide to use Steak over RSpec alone? Do you have any issue ramping up new developers with the Steak syntax?
1. It seems to take something that's already pretty straightfoward (RSpec) and just adds a couple keywords.
2. You're writing code when you should be describing features. Trying to remember where to put an underscore or what should be a symbol makes it harder to focus on describing the feature.
3. It greek to any non-developer. If you tried e-mailing this to a product owner or a user they would ask why you're sending code samples.
I know you addressed #3 in your blog post but why did you decide to use Steak over RSpec alone? Do you have any issue ramping up new developers with the Steak syntax?