SpecFlow vs. Tricentis Testim Salesforce

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.

Incentivized

My organization heavily customizes Salesforce to align it with specific business processes, adding custom fields, workflows, and triggers. With each Salesforce release or customization update, we need to ensure that existing functionalities and customizations remain intact.Tricentis Test Automation for Salesforce excels in this scenario. Its ability to create and execute comprehensive regression test suites efficiently ensures that customizations don't introduce unexpected issues or regressions. We can automate the validation of custom workflows, triggers, and data integrity, saving time and reducing the risk of errors.

Incentivized

• 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.

Incentivized

• Creation of Salesforce objects automatically
• AI-powered Smart locators
• Creation of test cases and modification is so easy compare to any other tool

• 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.

Incentivized

• The available documentation and learning resources are not extensive enough.
• The tool lacks sufficient customization options for creating and managing test cases.
• Limited integration with other tools and platforms.

Incentivized

We will renew but hope they improve their mobile experience.

Incentivized

Very good tool, first of this kind so no element to compare but still very good tool. It allows us to gain a lot of time and to be very deep in the testing phases

Incentivized

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.

Incentivized

We selected Tricentis Test Automation due to it's ease of use. It was the pricier option out of the competitve pool, however, it was important for us to have a scalable solution that integrated with all of our technologies and platforms. It was the most user-friendly tool and took the least amount of time to onboard individuals.

Incentivized

• 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.

Incentivized

• Improved productivity of QA team a lot
• Efficiency of test automation scripts gone up
• Automating test cases is so easy and reduced lot of efforts