[test] Each task defines own input and output

ManageIQ / floe

Floe is a runner for Amazon States Language workflows

Apache License 2.0

0 stars 6 forks source link

[test] Each task defines own input and output #123

Closed kbrock closed 1 year ago

kbrock commented 1 year ago

Overview

Add a helper so all the relevant fields are defined in one place in the spec.

Reasoning

I want to focus on the Task's output and how we parse it.

Unfortunately, the success, output, and other parameters are scattered around the spec file.

I added a helper method so all of the declarations for a test are inside the test. This made the link from the input to the output more obvious for me.

No Changes

This did not add or change any tests

miq-bot commented 1 year ago

Checked commits https://github.com/kbrock/floe/compare/aee729e95e141c6c5794d7d75bff2cadec15725a~...15817b7ae7608d96d452df29f5b29c509cb461f8 with ruby 2.6.10, rubocop 1.28.2, haml-lint 0.35.0, and yamllint 1 file checked, 0 offenses detected Everything looks fine. :star: