![]() ![]() These are valid: application/json" if I didn't specify it. The testing strategy uses AWS ECS Fargate, AWS CodeBuild and CodePipeline for continuous integration and delivery, Postman for testing, and TestRail for reporting. ![]() I know it's late, but I hope this will also fix the issue for you.ĮDIT : Having looked more into it, it seems that the API I was calling required that I specifically mention content-type: application/json, receiving "Invalid content type (application/octet-stream). March 2021 Automating your API Testing with Postman and Testrail On AWS Fargate Let’s automate some API testing. This solution satisfied my API, which now sends back the proper message. While it takes a little more time up front - we suggest using Connector Builder to make it faster to build Postman and Rally integrations down the road. On the other hand, it will include it if I put curly brackets as the body : To get data in and out of Postman and Rally, use one of our generic connectivity options such as the HTTP Client, Webhook Trigger, and our Connector Builder. Making my own tests with Logic Apps and Postman, I came under the conclusion that Logic Apps will ignore the Content-Type Header for a POST if the body is empty, as my API requested. I also had a similar issue with a POST request where the Content-Type Header I was sending was not received by the API, sending me back an incorrect data-type error. In fact as documented, it should be working - see "Omitted HTTP headers" here: I can only conclude my first Logic App isn't sending out the header I need it to. As another test, if I hit the second Logic App with a request sent via Postman, one that I've verified contains a "Content-Type" header, then the second Logic App shows it received my "Content-Type" header. Sure enough, no "Content-Type" header is being returned by that second Logic App. I know Logic Apps isn't sending this header because as a test I redirected the request to point to a second Logic App, which just returns any headers it receives. Unfortunately it doesn't look like Logic Apps is actually sending out the "Content-Type" header, so NetSuite doesn't know how to respond, and our integration fails. NetSuite can then interpret that and send its data back as JSON. So in the request, I add a "Content-Type" header with a value of "application/JSON". Visual Studio Code Extension Run k6 tests from VS Code. Empower your development workflow with IDE extensions. IDE extensions Code k6 scripts in your IDE of choice. Browser Recorder Record a user journey to base your k6 test. For NetSuite to respond to the GET request, it needs to know how we want its response returned - as XML, as JSON, etc. Codeless UI tool to generate a k6 test quickly. GET data from external services, such as NetSuite. Logic Apps can perform REST operations to e.g. We have a REST integration running between Microsoft's Logic Apps service (on Azure) and our NetSuite tenant. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |