Claris' FileMaker is presented as a Workplace Innovation Platform, and is used to create a custom app. Manual processes can be automated with Claris FileMaker Pro, and apps can be created to manage contacts, track inventory, organize projects, etc.
$21
per month per user
Visual Studio Test Professional
Score 7.0 out of 10
N/A
An add-on for the Visual Studio IDE, Visual Studio Test Professional subscription helps teams drive quality and speed. It includes test case management and collaboration features that streamline quality control and support continuous delivery.
$2,169
for the first year (renews at $869)
Pricing
Claris FileMaker
Visual Studio Test Professional
Editions & Modules
Platform Subscription
$21
per month per user
Individual desktop license
$594
one-time fee
No answers on this topic
Offerings
Pricing Offerings
Claris FileMaker
Visual Studio Test Professional
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Claris FileMaker
Visual Studio Test Professional
Features
Claris FileMaker
Visual Studio Test Professional
Low-Code Development
Comparison of Low-Code Development features of Product A and Product B
If your company is really small, I can understand the need for a product like this. However, I would go for MS Access... FileMaker Pro can not be integrated with other systems (like MS Access can at least be handled by C# for instance, and can be integrated with MS Excel or even SQL server). I'm really not sure in what scenario one would choose for FileMaker Pro. If your application or company grows bigger, you're going to have a problem to move to another environment. Also, the fact that only one person can work with the backend at any given time is a problem in a somewhat larger company.
It would be well suited if we used it with Azure DevOps as we can effortlessly integrate the test cases and even stories or tasks to stay on track with our work. Those test cases can even be reused across multiple projects. Using any other third-party tools, such as Jira, can be less appropriate, as it's not a Microsoft tool, and its capabilities will be limited.
The relational database management system makes the program highly customizable to fit the needs of any product. You can add a ton of information to each record and update your inventory on a regular basis with an Excel import or manually inside of the record. It has the capability to incorporate barcoding, which can manage your available inventory with ease.
The scripting language allows FileMaker to automatically calculate complex algorithms automatically or generate report outs with the click of a button. This allows for greater UI, especially with active users who are not familiar with writing code. Almost all of our internal data is linked to the FileMaker database
The server license allows many users to update the database in real time, which is handy if your inventory is constantly changing. We have users with Macs, PCs, iPhones and handheld tablets linked to our FileMaker database and they are updating the information constantly throughout the day.
If you invest some time into formatting and scripting the database, there is a high ease of use for users without knowledge of any programming or FileMaker itself.
Developer features need to be beefed up - namely adding the ability to search code for a phrase or keyword and the ability to do the same in the "relationship graph" in the database.
Add ability for users to edit the same table record at the same time by version control.
Allow Filemaker Server to use more than 1 core; currently multi-processing is not supported and it can be tricky to find just the right server to support the application you've built to the fullest capacity.
The user community of the Visual Studio Test product is weak. For instant problems with this product, it is necessary to quickly reach the source of the error.
Licence fees need to be more reasonable. License prices need to be reduced so that they can easily compete with free testing tools.
It it not really up to me but my opinion does have some weight in the decision and the reason I would renew my use FileMaker Pro 8.5 is because I am finally getting used to it! Now that I have been working with the program, tasks have become quicker and projects are getting done faster. File Maker Pro 8.5 really is a versatile tool and I think we are just scratching the surface with it's abilities.
It's almost what it should be after so may years and with Apple's longevity and strength behind it. For people who earn their living based on efficiency I think there are too many developer obstacles that waste time and therefore money.
It is very usable if you are familiar with Visual Studio to begin with. If you are new to the interface, it can be a long ramp up period for Testers not used to the GUI. There is always the web option which seems to be more intuitive for many Testers.
The forums are great with lots of helpful experts and the staff monitor them to provide help where needed. There have been a couple of unique technical issues I've had to deal with that I haven't been able to get resolved so I chose to score this a 9 instead of a 10.
Visual Studio Test Professional is backed up by the full support of the Microsoft Corporation. That means twenty-four/seven customer support by quality, highly-trained professionals who understand every possible issue that you have experienced before. They are nice, efficient, and highly professional. I recommend them.
Suggest you use an iterative R.A.D. or AGILE development approach. (i.e. rather than writing a gigantic spec for a system, then building it). FileMaker facilitates quick prototypes. Developing an example, then allowing users to "try it out" is a snap.
FileMaker is still the quickest way to go from zero to having a minimum viable working solution. Simple solutions can be built in as little as a afternoon of development. It is the only tool I am aware of which allows tech savy end users with domain knowledge to build bespoke apps for their businesses without undertaking professional software development training.
The visual Studio Test tool is faster than other tools. Since the development and testing processes are in one tool, it is more profitable in terms of cost. It is more inconvenient to write a test case in DevOps.
We are a more agile company because of FileMaker. A few of us who are tech-savvy enough to manage the database (but are not professional developers) can make needed adjustments to our database without having to employ an in-house developer or contract with a 3rd party. As our business processes evolve and change, it's easy to update the database to accommodate those changes.
One of the positive ROIs of Visual Studios is the fact that it makes producing our work at a quick rate, things like Intellisense make our work get produced at a much higher rate which is good for our return of investment.
Testing by the developers has increased by 23%, we now take the time to actually test our product before we send it to our QA people.
I am not aware of any negative ROI aspects to our company that have been found.
