Closed zsiddique closed 7 years ago
Yea we noticed the same difference between real SQS and Elasticmq tests. I have raised a PR which changes the Elasticmq behaviour to be in line with SQS so hopefully nobody runs into this in the future :)
Should be fixed in 0.13.4
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_ReceiveMessage.html So the AWS API is a little vague on this but testing shows that when ReceiveMessage is called with no MessageAttributeName defined ReceiveMessage returns messages with no MessageAttribute. But elaticmq will return MessageAttribute regardless what is asked in MessageAttributeName. This caused a problem for us as we are using elasticmq to test our usage of SQS and we had a bug in which we neglected to request an MessageAttribute but would work in testing but failed once we got to integration testing with real SQS. Example using boto. First with Elasticmq
With AWS SQS: