--- description: Ranorex Studioを実際に使用したユーザーのレビューから、製品の機能や価格、メリットデメリットをご覧いただけます。類似製品との比較も簡単、ぴったりのSaaSが見つかるはず！ image: https://gdm-localsites-assets-gfprod.imgix.net/images/capterra/og_logo-e5a8c001ed0bd1bb922639230fcea71a.png?auto=format%2Cenhance%2Ccompress title: Ranorex Studioとは？ | 機能や料金、導入事例をご紹介【キャプテラ】 --- 現在地表示: [ホーム](/) > [テスト管理ツール](/directory/34315/test-management-tools/software) > [Ranorex Studio](/software/173144/ranorex-studio) # Ranorex Studio Canonical: https://www.capterra.jp/software/173144/ranorex-studio ページ：1 / 6\ 次へ: [次ページ](https://www.capterra.jp/software/173144/ranorex-studio?page=2) > Ranorex Studioは、デスクトップ、Web、モバイル・アプリケーションでのエンドツーエンドのUIテストを高速化するツールセットです。 > > 評価：123人のユーザーによる評価は**4.4/5**。**おすすめ度**で最高の評価。 ----- ## 概要 ### Ranorex Studioの対象ユーザー 顧客には、個々のテスター、コンサルタント、テスト・オートメーション・エンジニア、QAマネージャー、大小規模の組織の開発者が含まれます。顧客に共通するのは、高品質のソフトウェアに対する情熱です。 ## 簡単な統計と評価 | 測定基準 | 評価 | 詳細 | | **総合評価** | **4.4/5** | 123 レビュー | | 使いやすさ | 4.3/5 | レビュー全体に基づく | | カスタマー・サポート | 4.5/5 | レビュー全体に基づく | | 価格の妥当性 | 4.3/5 | レビュー全体に基づく | | 機能 | 4.3/5 | レビュー全体に基づく | | おすすめ率 | 80% | (8/10 おすすめ度) | ## 企業情報 - **キャプテラについて**: IDERA - **設立**: 2011 ## ビジネスコンテキスト - **価格プラン**: $4,650.00 - **価格モデル**: (無料のトライアル) - **対象となる企業**: 自営業, 2～10, 11～50, 51～200, 201～500, 501～1,000, 1,001～5,000, 5,001～10,000, 10,000+ - **デプロイとプラットフォーム**: クラウド、SaaS、ウェブベース, Windows（デスクトップ）, Windows（オンプレミス）, Android（モバイル）, iPhone（モバイル）, iPad（モバイル） - **サポートされる言語**: 英語 - **利用可能な国**: アイスランド, アイルランド, アゼルバイジャン, アフガニスタン, アメリカ合衆国, アラブ首長国連邦, アルジェリア, アルゼンチン, アルバ, アルバニア, アルメニア, アンギラ, アンゴラ, アンティグア・バーブーダ, アンドラ, イエメン, イギリス, イスラエル, イタリア, イラク さらに209件 ## 機能 - コラボレーションツール - ソフトウェア・テスト管理 - テストスクリプト・レビュー - データの可視化 - パフォーマンス・テスト - ワークフロー管理 - 並列実行をサポート - 品質保証 - 階層ビュー ## 統合 (合計12件) - Bamboo - BrowserStack - Bugzilla - ConnectALL Integration Platform - Jenkins - Jira - Sauce Labs - Selenium IDE - SpiraTeam - TeamCity - TestBench - TestRail ## サポートのオプション - メール/ヘルプデスク - FAQ/フォーラム ## Category - [テスト管理ツール](https://www.capterra.jp/directory/34315/test-management-tools/software) ## 関連カテゴリー - [テスト管理ツール](https://www.capterra.jp/directory/34315/test-management-tools/software) - [テスト自動化ツール](https://www.capterra.jp/directory/30609/automated-testing/software) - [性能テストツール](https://www.capterra.jp/directory/31124/performance-testing/software) - [負荷テストツール](https://www.capterra.jp/directory/32135/load-testing/software) ## 代替製品 1. [Tricentis Tosca](https://www.capterra.jp/software/120858/tricentis-tosca) — 4.2/5 (18 reviews) 2. [TestMu AI](https://www.capterra.jp/software/170732/lambdatest) — 4.6/5 (543 reviews) 3. [Katalon Studio](https://www.capterra.jp/software/1018018/katalon-studio) — 4.4/5 (706 reviews) 4. [Cypress](https://www.capterra.jp/software/168276/cypress) — 4.7/5 (67 reviews) 5. [Tricentis Testim](https://www.capterra.jp/software/165430/testim) — 4.6/5 (50 reviews) ## レビュー ### "Ranorex: Easy and Powerful Software Automation Tool" — 5.0/5 > **Deepakkumar N.** | *2019年2月14日* | 運輸、トラック、鉄道 | おすすめ評価：9.0/10 > > **良いポイント**: \[My Organization got 20+ licenses for Ranorex after trying it out for 30+ days for free - I am neither related to Ranorex nor is this a paid review\] Pros: 1. The tool is comparatively easy to learn \[Compared to QTP-UFT\]. 2. There is amazing support available from Ranorex - This was possible because of the 20+ licenses purchased and Ranorex Representatives coming in to solve our specific queries. 3. The tool is powerful in the sense that it can help recognize and work with / take care of blinking objects / tooltips which disappear quickly / dynamic object which are difficult to recognize from automation perspective. 4. I like the idea that the tool gives you the power to start easy \[simple recordings\] and then you can take charge \[for more complicated stuff - to harden the solutions\] by designing User Code Methods / Modules. > > **改善点**: 1. The tool is not cheap. \[But worth the money spent\] 2. Every-time you need to execute your code / automation recording, the whole solution needs to be re-built which takes time and is annoying. 3. Using the GitHub tool along with Ranorex for maintaining the code from various developers / maintaining versions and releases can be tricky and needs a little practice and patience. > > Our organization works on a legacy desktop project using some relatively old Java Elements for its front-end design combined with C++ backend using CORBA calls. Some of the GUI objects are relatively new. So our project has a mix of legacy / old Java objects \[swanky toolbars\] / new Java objects and c++ for backend. Overall, the learning curve for the Ranorex Automation Tool was not steep. I genuinely enjoy the coding and designing part for the project using this powerful tool as a senior architect for the project. My Genuine Advice: Before purchasing, please use the free version of the tool and try building up an object repository for the system under test which can give you the confidence whether this tool is right for your project or not. ----- ### "The best tool for mobile testing automation" — 4.0/5 > **Katarzyna** | *2019年10月4日* | 写真 | おすすめ評価：8.0/10 > > **良いポイント**: Complexity. The tool is proffesional (we have been used free Katalon Studio earlier which was buggy). It is very useful for mobile testing automation for our Android nad iOS apps. Tests are stable and easy to maintain. > > **改善点**: Unfortunately - the costs. This tools isn't cheap. Also, Ranorex because of its complexity, it is not easy to at the first glance. You need some training and time to learn how to prepare tests. > > As I described above - Ranorex is highly useful for creating and executing stable mobile tests on our devices (Android, iOS). In future we plan to use this tool for web automation, too. ----- ### "Months without a solution ..." — 1.0/5 > **認証済みレビュアー** | *2021年11月18日* | コンピュータ・ソフトウェア | おすすめ評価：0.0/10 > > **良いポイント**: Although the first year with Ranorex was fine and increased our productivity overall, the first problem that appeared after the standard support period expired gave the whole cooperation a bad taste. > > **改善点**: Apart from the fact that if you don't buy support continuously and the problem appears after a year and a half, for example, you have to buy support for the whole past period just to get someone to talk to you, after buying support and reporting the problem it took them half a year to even get to the problem analysis during which we were without a working application. Several times we had to tediously report the same problem over and over again as we were shuffled around by support teams who had no continuity for our support case. > > When our support expired again for a period during which we could not use the program, Ranorex referred us to another support purchase, still without a working solution. This is totally unacceptable and definitely not a pro-customer approach. ----- ### "Fred's input of Ranorex" — 5.0/5 > **Fred** | *2025年6月17日* | 石油、エネルギー | おすすめ評価：10.0/10 > > **良いポイント**: The spy and tracking features are great When a script fails having a green check mark to show what is working in playback mode vs a red "x" next to what fails in the xPath just speeds up the debugging process > > **改善点**: Moving a project to another machine and merging two projects. Honestly, I have not done this enough to feel 100 % comfortable with it. I hope to get more time to do this in my present job > > I first started using Ranorex in 2015 at Kapsch TrafficCom. In 2021 I brough Ranorex to INPO. I have used IBM Witt, WinRunner, Xrunner, Rational Robot, QTP and UAT and by far I love using Ranorex the most. I cannot wait to see what Ranorex will do with AI in the coming years ----- ### "Ranorex rocks\!" — 4.0/5 > **Pavel** | *2018年11月14日* | コンピュータ・ソフトウェア | おすすめ評価：10.0/10 > > **良いポイント**: What I really like about Ranorex is its wide coverage of technologies, relative easy to learn and use UI, pretty robust and reliable element recognition and very helpful and responsive support. In fact, their proactive and friendly support was one of the major decision points for me. I'm working with Ranorex since 2012 and so far, I was always able to achieve my goals (automating mainly desktop and web-based apps). > > **改善点**: Unfortunately, I really don't like Ranorex API documentation. While the general Ranorex user guide is great both for novice and advanced users, advanced coders may find Ranorex API documentation pretty inadequate and lacking samples. Luckily, Ranorex user forum is already filled with tons of use cases and code examples. Still, Ranorex API documentation really needs an overhaul. ----- ページ：1 / 6\ 次へ: [次ページ](https://www.capterra.jp/software/173144/ranorex-studio?page=2) ## リンク - [Capterraで表示する](https://www.capterra.jp/software/173144/ranorex-studio) ## このページは以下の言語で利用できます | ロケール | URL | | de | | | de-AT | | | de-CH | | | en | | | en-AE | | | en-AU | | | en-CA | | | en-GB | | | en-IE | | | en-IL | | | en-IN | | | en-NZ | | | en-SG | | | en-ZA | | | es | | | es-AR | | | es-CL | | | es-CO | | | es-CR | | | es-DO | | | es-EC | | | es-MX | | | es-PA | | | es-PE | | | fr | | | fr-BE | | | fr-CA | | | fr-LU | | | it | | | ja | | | nb | | | nl | | | nl-BE | | | pl | | | pt | | | pt-PT | | | sv | | ----- ## 構造化データ