You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a code example engineer (internal) or customer (external), I want to be able to run a subset of SDK code example tests by running a generic command with a tag, i.e. <test-command> <tag>
You could accomplish this in a few different ways:
a bash script that tags a tag parameter, e.g. ./test.sh <tag>
a language test framework command using an include tag: dotnet test --tag @integ @unit
the same framework as above but with an exclusion tag: dotnet test --tag ~@integ
Which tests should I tag?
You can decide this for yourself! Just make sure your own tagging strategy that allows you to isolate tests that are:
are automation-friendly
can run consistently without error.
What is "automation-friendly"?
This refers to tests are can be executed remotely in an Isengard account with no previous setup required. This would include both unit tests and integration tests.
What does "without error" mean?
It means you can run the test in the presence of AWS credentials from our local CLI environment and it will pass without error consistently.
Acceptance criteria
I know this is done when:
I can pass a string tag value to my tests to invoke a subset of tests with that tag.
Bonus points for:
exclusion tags (e.g. ~@quarantine)
multiple tags at once (e.g. @integ @unit)
Output
Tag a story with 'integration' and 'unit', or tag a test in a story that doesn't work with 'quarantine'
The text was updated successfully, but these errors were encountered:
User story
As a code example engineer (internal) or customer (external), I want to be able to run a subset of SDK code example tests by running a generic command with a tag, i.e.
<test-command> <tag>
You could accomplish this in a few different ways:
./test.sh <tag>
dotnet test --tag @integ @unit
dotnet test --tag ~@integ
Which tests should I tag?
You can decide this for yourself! Just make sure your own tagging strategy that allows you to isolate tests that are:
What is "automation-friendly"?
This refers to tests are can be executed remotely in an Isengard account with no previous setup required. This would include both unit tests and integration tests.
What does "without error" mean?
It means you can run the test in the presence of AWS credentials from our local CLI environment and it will pass without error consistently.
Acceptance criteria
I know this is done when:
Bonus points for:
~@quarantine
)@integ @unit
)Output
The text was updated successfully, but these errors were encountered: