Example intergration tests

kbrock commented 2 months ago

fixtures / integration tests

Overview

A number of asl files are working differently in floe from AWS State Language runtime.

Here are some fixtures to ensure that both environments work the same.

File Naming

test-[state]-[status]-comment

State

The State is the State under test. We currently have tests for Pass, Fail, Task, and Choice.

Status

The pass files contain a number of tests run inline.
The fail tests take a parameter like {"test":1} to subequent tests. Since these throw an uncatchable runtime error, we need to execute each individually.
The invalid tests have a parser error. They are not json errors, but rather semantic errors.

Future

runner script

I currently have a runner script ref. Though working, it is still a WIP. I can add to this repo if desired.

Tasks

I have tests for tasks, but am unsure the best way to post the hello world container. It outputs to stderr, stdout, and changes the return code.

Can't remember where we had agreed upon putting this.

Fryguy commented 2 months ago

If these are meant for tests, can we move them under the spec directory? I think of examples as more user-facing references. I don't think users want to create invalid asls, which is what most of these are.

kbrock commented 2 months ago

These are use cases to testing that we are produce the same errors / results as aws state machines.

I'll move to tests

miq-bot commented 2 months ago

Checked commits https://github.com/kbrock/floe/compare/3096c10936c2722cc45c90dfcdd2240cbba98e4a~...7bedfbab7ecb1cc7b442dde4522be4a6e248764d with ruby 3.1.5, rubocop 1.56.3, haml-lint 0.51.0, and yamllint 0 files checked, 0 offenses detected Everything looks fine. :cookie:

kbrock commented 2 months ago

update:

moved new examples into spec/fixtures (the existing ones in there are actual examples)

kbrock commented 1 month ago

I'm keeping a running tally of examples to validate our behavior in the future

ManageIQ / floe