Postman, headquartered in San Francisco, offers their flagship API development and management free to small teams and independent developers. Higher tiers (Postman Pro and Postman Enterprise) support API management, as well as team collaboration, extended support and other advanced features.
$0
SpecFlow
Score 9.9 out of 10
N/A
SpecFlow is an open source BDD for .NET. that aims to bridge the communication gap between domain experts and developers by binding readable behavior specifications to the underlying implementation.
N/A
Pricing
Postman
SpecFlow
Editions & Modules
Postman Free Plan
$0.00 US Dollars
Postman Basic Plan
$12 US Dollars
per month per user
Postman Professional Plan
$29 US Dollars
per month per user
Postman Enterprise Plan
$99 US Dollars
per month per user
No answers on this topic
Offerings
Pricing Offerings
Postman
SpecFlow
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
1. Postman Free plan: Start designing, developing, and testing APIs at no cost for teams of up to three people.
2. Postman Basic plan: Collaborate with your team to design, develop, and test APIs faster; $12/month per user, billed annually
3. Postman Professional plan: Centrally manage the entire API workflow; $29/month per user, billed annually
4. Postman Enterprise plan: Securely manage, organize, and accelerate API-first development at scale; $99/month per user, billed annually
Postman is good for organising your API credentials, vendor settings, environments etc. It's also a good way of getting stared with APIs as you get to use a GUI which can help you understand what we mean by a 'body' or 'bearer token'. I think people generally gravitate towards GUI tools for getting started in a new technology area.
It is best suited for implementing the automated test cases in a human readable form so it's easy for non-technical members of the team and stakeholders to understand the test cases, features and the functionalities of the application. Automation of Integration tests and End to End tests are good use case. It is less appropriate or situations where the focus is only on the writing and maintenance of unit tests.
It has opened a door for me to explore more out of it, as it is associated with so many APIs that I never felt any difficulty in finding the right API template, which are well organized and easily available.
It is very secure to use and provides great services which are user-friendly.
Due to this software I have got rid of the excessive emails and the slack channels, Now I am using my own private API and even it give me an option to produce my personal Postman’s API Builder from its Private API Network and this features has shared my excessive workload.
Versatility to be used in combination with different kinds of automated testing like automated performance testing, API testing, UI testing etc. I use JavaScript, Selenium, C#, email testing libraries, database testing libraries in combination with BDD with SpecFlow. I am able to use all these with SpecFlow to make my automation framework to be able to automate any kind of automated testing.
It provides different widely used runner options like NUnit, XUnit etc. Before I started to work on establishing proper test automation in my workplace, the previous automation framework (non-BDD based) as well as unit tests used NUnit runner. The transition to using BDD was smooth because we could use the same runner and there were no compatibility issues.
The auto-complete feature is good. I use it with Visual Studio as well as Rider and I don't have to recall the entire Gherkin statements. I just type a few words and the entire Gherkin statement implemented in framework is auto-suggested by SpecFlow. It saves time and context switching.
SpecFlow does not accepts optional input variables in the methods defined during Gherkin statement implementation. Cucumber supports optional input variables in the methods defined during Gherkin statement implementation.
The tests identified while using SpecFlow with NUnit removes all white spaces in the scenario names. It makes the tests less readable. If the white spaces are not auto-removed, it would be much better for readability as well as their actual identification in the repository.
1. Friendly user friendly - when I started using Postman, I was a beginner to the API world, and it gave me a friendly view to begin its usage 2. Postman offers many features, including API testing, monitoring, documentation, and mock servers 3. Environment variables simplify testing across multiple environments (dev, prod) without repetitive configuration.
There is a lot of in-depth documentation for Postman available online, including detailed guides with screenshots and videos. They provide example APIs for new users to explore while learning how to use the tool. Generally, bugs in the client are quickly addressed through frequent free updates. Community and professional support options are available - most of the time, the free/community level support is adequate
Previous to using Postman, I would either use browser tools directly, or write an in-house tool to send requests. Postman eliminates that need while providing a much better experience and more features. At the base level, Postman is as simple as typing in the address as you would in a browser. Authentication can be provided simply as well.
SpecFlow is .Net based which supports C#. Behave is Python based. Cucumber is Java based. Ghost Inspector is no-code based but provides very limited testing features. We wanted to implement BDD so we rued out using Ghost Inspector. Most of the developers in my team are C# experts so it was decided for everyone's comfort to go for SpecFlow rather than Behave or Cucumber. It's import to have technical experts in the language of the automation framework because there are many situations where the solutions to the test automation needs are not straightforward and implementing those requires expertise in the related programming language.
Postman is free (although there's a paid tier that offers more features) so using it for testing APIs comes with little to no risk (besides learning curve).
The learning curve is a little steep for non-developer users, but developers should find it easy to pick up and use right out of the box, so to speak.
Everyone stays on the same page regarding the behavior of existing functionalities whether it be technical or non-technical individuals. So there is less need for multiple people to get involved which saves time and thus money.
Reusing the same code through the implemented Gherkin statement saves test automation time and thus reduces cost.
We combine SpecFlow with other opensource testing technologies to make our automation framework more versatile which further saves costs for us.
