• Postman Version: 4.9.0 for Chrome and 4.9.1 for Mac • App (Chrome app or Mac app): Both • OS details: OS X EL CAPTAIN. Version 10.11.6 and Chrome Version 43.0.2357.65 (64-bit) • Is the Interceptor on and enabled in the app: On and enabled in Chrome and not enabled in Mac • Did you encounter this recently, or has this bug always been there: We just started testing our new service • Expected behaviour: Both Chrome and Mac versions behave in the same way. • Console logs ( for the Chrome App, View->Toggle Dev Tools for the Mac app): No errors in both console. • Screenshots (if applicable): NA First of all, thank you so much for a great product!! It is saving a lot of time for our team. You guys are the best!! My team came across an issue recently for file upload using web service that we created. ![]() Chrome REST Client Alternatives| Insomnia REST Client — Aug 20, 2016 This means that popular Chrome-based REST clients like Insomnia (2.0) Best Postman Alternatives: 25+ API / REST Development tools — Mar 18, 2018 Popular Alternatives to Postman for Mac, Windows, Linux, Web. Ever since I upgraded to Postman 0.9.6 I can't replicate user sessions because chrome doesn't allow postman to get user cookies. However, they have decided to 'work around' this issue by created another plugin called Postman Interceptor that routes your postman request and grabs the user cookies. The web service is written as a plugin in Jive using J2EE, Spring, CXF. The web service is working fine when using the Postman-Chrome. But, it is giving error from Jive while using the Postman-Mac. When tested using the cURL command, it is working fine when using multipart/mixed, but throwing the same Jive error while using multipart/form-data. Sample cURL command: curl -X POST -H 'Authorization: Basic YWRtaW46YWRtaW4=' -H 'Content-Type: multipart/mixed' -H 'Cache-Control: no-cache' -H 'Postman-Token: 12fabee9-c356-a779-41bb-8e6d12eb8a29' -F '[email protected]' ' So, we figured, the issue is happening as Jive has its own parser using Struts 2. And the CXF page says we have to disable the Struts 2 parser, if we use multipart/form-data. So, it makes sense that the cURL command is working with multipart/mixed and not with multipart/form-data. ![]() (Struts parser is invoked only for form-data) The question we have is how does the Postman-Chrome works when using multipart/form-data or any other multipart; when Postman-Mac never works for any multipart content type (form-data, mixed. Can you please help us with this dilemma? If you can send us the difference in the (POST) calls between Postman-Chrome and Postman-Mac, it will be very helpful. I recently interviewed, an SDET at about how she uses automation to test video games. It turns out that most of the testing she needs to perform is a good fit for automation are back-end, API-type tests, and her tool of choice is chrome. What is Postman Chrome? Postman Chrome is a rest client that started off as a potman chrome extension browser plugin but recently came out with native versions for both Mac and Windows. At a high level, you can use it to send a post request to your web server and it gives you the response back. It allows you to set up all the headers and cookies your API expects, then check the response when it comes back. That’s its basic functionality, but it also has lots of other features built into it like excellent cookie management that can sometimes be hard to manage with other API tools. Postman chrome plugin and app supports every HTTP method you can think of — including some you might even know about. For API validation, it has basic checking you can do when you receive the response. A common example of this is when you send a request to an API and get a response back, you verify that it returns a OK status, or you make sure that the response contains a certain string in it. Exploratory API Testing Using Postman When most folks think of automation they don’t necessarily think of using test automation tools, but that’s a mistake. In Amber’s experience, when she is performing back-end testing she finds herself using more and more to assist her in exploring her team’s APIs. It really helps her to learn what an API does. The main way she does this is by tweaking the API request to see what comes back. It’s a really useful tool for both automated and manual testing. She explained that she is often given a scenario — load testing a web server, for instance. In situations like this, you don’t always know a whole lot about what the web server is supposed to do; you just expect to load test it without any context. To understand how to create a realistic test, you need to really look into the game to see how it’s communicating with the server, then try to replicate those calls using a tool like Postman. From there it’s just a matter of seeing what’s there and determining what works and what doesn’t. Amber also mentioned that in her experience with automation, 95% of the bug finding happens when she’s writing the automation, then it just runs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2019
Categories |