Parameterized steps

Sometimes you have steps which repeat themselves but have constant arguments that can be determined during story definition.

For example a step which uploads a file to an S3 bucket can be parameterized by the S3 bucket it should be uploading to. The alternative would be to create a step which simply sets the context to a constant before the execution of the upload step. This is verbose and frankly unnecessary.

Suggested syntax:

class Foo:
  @story
  @arguments("file")
  def do(I):
    I.upload_to_s3.partial(bucket_name='special_files')

  def upload_to_s3(self, ctx, bucket_name='default'):
    pass

[proofit404]

The purpose of our DSL is an explanation of the business process in mostly human language. Coupling values to it is a mistake in my opinion. There is a lot of places where we could put constants in Python. Making story spec one of them isn’t what I want.

[thedrow]

Because sugar is what makes open source libraries so sweet.

Seriously though, typing less is always an objective when creating libraries.