Search for a command to run...
I am a Lead Engineer from India. Love to blog about serverless and help teams design and develop serverless architecture. An AWS cloud practitioner. Blogs about AWS Services utilising AWS CDK, CloudFormation, Terraform.
No comments yet. Be the first to comment.
Transformers, the backbone of many state-of-the-art NLP models such as BERT, GPT has revolutionized the way we approach natural language understanding tasks. One key innovation in transformers is their ability to handle entire sequences of tokens sim...
When an User prompts the questions to the LLM, it produces the response based on the training data. The pre-trained LLM data is its parametric data. It might not have an context specific to our query. LLM still produces an answer confidently. It is t...
In the fast-evolving field of artificial intelligence, Large Language Models (LLMs) have rapidly transformed how we approach language processing. These models, such as ChatGPT, Claude, and Bard, have proven their utility across a range of application...
Amazon S3 is a powerful, scalable storage service, but when multiple clients or processes attempt to write to the same S3 object simultaneously, things can get tricky. Since S3 doesn’t natively handle concurrent writes or provide object locking, it’s...
When working with distributed systems in a microservice architecture, we must always architect our services with failure in mind. When the transaction happens between a microservice, we have to handle the failures. The Saga pattern can be used in a f...
AWS Step Functions offers an array of testing and debugging tools. In this blog post, we'll focus on the TestState API.
TestState API helps us to test a single state in the state machine workflow. So, we can test a state without creating a state machine and execute the complete flow. This helps resolve common errors such as path issues, and input/output issues at the development time and at a fast pace.
The following states are supported for TestState.
Pass
Wait
Task
Choice
Succeed
Fail
Step Functions offers three distinct inspection levels: INFO, DEBUG, and TRACE. The different inspection levels, provide us the right amount of detail to suit our debugging and validation needs.
INFO: At this level, we receive essential information about the state execution, including the status and the next state to transition to.
DEBUG: At this level, it provides additional insights into the state execution. Beyond the status and next state, you gain access to intermediate details, especially useful when using input and output data processing filters like InputPath or ResultPath.
TRACE: At this level, it not only includes the status and next state but also provides deep into the intermediate and final data processing results.
We can use AWS CLI with TestState for testing each state of the state machine in silo.
Suppose, we have a passstate in our Stepfunction as shown below.
{
"Type": "Pass",
"Next": "Second State",
"Parameters": {
"payload.$": "$.customer.firstName"
}
}
To test this state, we can use below AWS CLI command
aws stepfunctions test-state \
--definition '{
"Type": "Pass",
"Next": "Second State",
"Parameters": {
"payload.$": "$.customer.firstName"
}
}' \
--role-arn arn:aws:iam::1234567843:role/example \
--input '{"customer": {
"firstName": "rahul",
"lastName": "lokurte"
}
}'
The output is as shown below.
{
"nextState": "Second State",
"output": "{\"payload\":\"rahul\"}",
"status": "SUCCEEDED"
}
As seen in this short blog, we can use the TestState API to test the individual states in a state machine which opens up a lot of opportunities for testing the step functions thoroughly.