--- description: Leapworkを実際に使用したユーザーのレビューから、製品の機能や価格、メリットデメリットをご覧いただけます。類似製品との比較も簡単、ぴったりのSaaSが見つかるはず！ image: https://gdm-localsites-assets-gfprod.imgix.net/images/capterra/og_logo-e5a8c001ed0bd1bb922639230fcea71a.png?auto=format%2Cenhance%2Ccompress title: Leapworkとは？ | 機能や料金、導入事例をご紹介【キャプテラ】 --- 現在地表示: [ホーム](/) > [テスト自動化ツール](/directory/30609/automated-testing/software) > [Leapwork](/software/162251/leapwork) # Leapwork Canonical: https://www.capterra.jp/software/162251/leapwork ページ：1 / 3\ 次へ: [次ページ](https://www.capterra.jp/software/162251/leapwork?page=2) > Leapworkのノーコード・テスト自動化とロボテック・プロセス・オートメーション (RPA) プラットフォームでビジネスとITのユーザーが反復プロセスを簡単に自動化することができます。 > > 評価：50人のユーザーによる評価は**4.3/5**。**おすすめ度**で最高の評価。 ----- ## 概要 ### Leapworkの対象ユーザー Leapworkは、デジタル・トランスフォーメーションの指針を持ち、品質保証 (QA) 環境やポスト・プロダクションのビジネス・ドメイン全体でスピードと品質を向上させたいと考えているあらゆる業界のグローバル企業にサービスを提供しています。 ## 簡単な統計と評価 | 測定基準 | 評価 | 詳細 | | **総合評価** | **4.3/5** | 50 レビュー | | 使いやすさ | 4.4/5 | レビュー全体に基づく | | カスタマー・サポート | 4.6/5 | レビュー全体に基づく | | 価格の妥当性 | 4.2/5 | レビュー全体に基づく | | 機能 | 4.3/5 | レビュー全体に基づく | | おすすめ率 | 80% | (8/10 おすすめ度) | ## 企業情報 - **キャプテラについて**: Leapwork - **ロケーション**: Copenhagen K, デンマーク - **設立**: 2015 ## ビジネスコンテキスト - **価格モデル**: (無料のトライアル) - **対象となる企業**: 自営業, 2～10, 11～50, 51～200, 201～500, 501～1,000, 1,001～5,000, 5,001～10,000, 10,000+ - **デプロイとプラットフォーム**: クラウド、SaaS、ウェブベース, Windows（デスクトップ） - **サポートされる言語**: 英語 - **利用可能な国**: アイスランド, アイルランド, アゼルバイジャン, アフガニスタン, アメリカ合衆国, アラブ首長国連邦, アルジェリア, アルゼンチン, アルバ, アルバニア, アルメニア, アンギラ, アンゴラ, アンティグア・バーブーダ, アンドラ, イエメン, イギリス, イスラエル, イタリア, イラク さらに209件 ## 機能 - コラボレーションツール - ソフトウェア・テスト管理 - テストスクリプト・レビュー - ワークフロー管理 - 並列実行をサポート - 要件管理 - 階層ビュー ## 統合 (合計14件) - Confluence - DevSuite - Dynamics 365 - Jenkins - Jira - LabVantage - Microsoft Azure - Microsoft Power BI - SAP Marketing Cloud - ServiceNow - Tableau - TeamCity - TestRail - Watson Campaign Automation ## サポートのオプション - メール/ヘルプデスク - ナレッジベース - 電話サポート - 24時間対応（オペレータ） - チャット対応有 ## Category - [テスト自動化ツール](https://www.capterra.jp/directory/30609/automated-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) ## レビュー ### "Leapwork: Scriptless Tool for Automation Quick and Fast" — 4.0/5 > **Rahul** | *2024年2月20日* | 情報技術、情報サービス | おすすめ評価：9.0/10 > > **良いポイント**: 1. Scriptless framework 2. Easy version tracking 3. Very good support in their website. 4. Reusable sub flow created by anyone in team can be resued by anyone else. > > **改善点**: 1. Image recognition can be improved. 2. Sending email using attachment can be made easier rather than using powershell. > > My overall experience has been good and we have been using it for more than 3 years now and we moved from standard license to enterprise one. ----- ### "Focus on making tests and not only writing test code" — 5.0/5 > **John** | *2019年9月5日* | 薬品 | おすすめ評価：10.0/10 > > **良いポイント**: I think that the codeless interface is a brilliant idea and increases the efficiency of the testing team significantly. For my team, where testing is just one of the responsibilities we have when upgrading and patching the product, we don't want to start training people up on programming languages so that they could start writings tests. With Leapwork the learning curve is very shallow and people can get started right away. I am impressed with the selection of blocks that have been included and haven't required any functionality so far that there wasn't either a block for or a could make a simple sub-flow for. The strategy editor, which is used to decide how to identify the GUI elements being manipulated, is really really clever\! > > **改善点**: The debugging functionality needs to be improved. When running complicated flows with mutiple sub-flows inside, when a bug occurs it is difficult to dig down into the sub-flow where the problem occured, and even when you've reached it there is no context specific data on the variables feeding into or out of the trouble making block. I don't think that their approach to customer support is correct, and I have spent hours spinning my wheels as I carried out long conversations with their support stuff via a chat window on their homepage. Some of the initial steps that are required, like making a test flow to log onto the Leapwork agent server, were not clearly explained. > > Leapwork has solved a big problem for my team in regards to performing our user acceptance testing on new releases and upgrades of the software are responsible for deploying. The platform feels a little immature at terms in terms of the community support but there is a very solid foundation there to grow on. ----- ### "Can't get anyone to acknowledge me from the company so..." — 1.0/5 > **Jonathon** | *2024年8月7日* | 病院、ヘルスケア | おすすめ評価：0.0/10 > > **良いポイント**: The functionality of the platform was as expected. We chose to engage with Leapwork to help us automate some web-based processes, and admittedly that's not their bread and butter. > > **改善点**: Lack of communication and customer service. > > After we signed the contract, we quickly realized that the workflows we were trying to automate were not stable enough to leverage the platform. That's on us. They reached out once, presumably when they could see that we were no longer using the platform to see if they could re-engage us, but it wasn't a fit. We told them on the call that the platform wasn't a fit and our intent was to not renew. Months after the contract term came and went, they invoiced us for the renewal via a canned email. I replied and said our intent was not to renew and there was never a reply. We received a series of canned emails with invoices and I replied to each asking for a human being to respond and acknowledge me, but that never happened. They have since sent our account to collections for the renewal, and invoiced us yet again for the next contract renewal. I know this company is all for automation, but it would be nice if you could work with a human when things aren't working. Even if the first notice was not in writing, they received several emails of our intent on the second renewal. They seem disorganized and overly automated. ----- ### "LEAPWORK Has Helped Us Create Better Software" — 4.0/5 > **Kyle** | *2019年12月10日* | 保険 | おすすめ評価：8.0/10 > > **良いポイント**: - Ability to create automated tests for a thick client - User friendly views for creating tests from a flowchart - The ability to scheduled tests > > **改善点**: - Scheduled tests couldn't deliver notifications to multiple emails - Email validation was very strict. - Electronic signature image recognition was slow and timed out frequently > > We are automating the tests for our digital contract platform to make sure our agents in the field always have a reliable software that doesn't have any bugs or issues. We have been able to create tests to cover all of our compliance for each state so that our agents and funeral homes are always 100% compliant with the contracts they create. ----- ### "Serious gaming" — 5.0/5 > **Koen** | *2019年12月5日* | 情報技術、情報サービス | おすすめ評価：8.0/10 > > **良いポイント**: Leapwork is a visual object oriented tool for creating flows that automate repetitive actions in the operation of software, both for desktop apps and for websites, ideal for testing\! No matter how simple or complex the flow, there are actually little restrictions because the set of building blocks is very complete where each block also has a rich set of options to specify its actual behaviour. Better yet, the set may be expanded with custom made reusable subflows as blocks for commonly executed general actions such as logging into an environment or application or opening specific web pages, ensuring that the flows remain easy to understand at each level and easier to maintain. An extensive set of examples makes it very easy to give it a go and when I do then encounter a problem in applying Leapwork, the helpdesk helps me out using a very efficient chat. Flows may be executed interactively on a desktop or laptop or on a server, on BrowserStack or on a Selenium Grid, but also may be scheduled to run automatically at specific moments. Also, these schedules may be started from DevOps or by calling the REST API from e.g. Powershell scripts. > > **改善点**: Leapwork is a very flexible and versatile tool that is fun to use. But when you flip that coin, it turns out it also is easy to make flows that are difficult to maintain. And yes, it takes some self-control not to step into this trap. But then, I made flows for adaptive websites that run on various window sizes and on test, acceptance and production sites ... all in the same flow\! The reason why complex flows sometimes are not easy to maintain is because Leapwork has only limited options to execute flows step-by-step. This makes it difficult to pinpoint the exact location in the flows where things go wrong and therefore need some tweaking. The tweaking itself is easy and straightforward, but finding out where and when and why is a challenge. Also, it is not easy to output specific information without the need to go through the complete log that the flow creates. > > We use Leapwork to run flows for regression testing whenever a software update is released to test, acceptance or production sites. Also, we use Leapwork to frequently run flows to verify that specific pages, functions or API's remain available. We consider it a challenge to specify which flows we need, rather than how we can create and maintain them ... thanks to Leapwork. ----- ページ：1 / 3\ 次へ: [次ページ](https://www.capterra.jp/software/162251/leapwork?page=2) ## リンク - [Capterraで表示する](https://www.capterra.jp/software/162251/leapwork) ## このページは以下の言語で利用できます | ロケール | 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 | | | ko | | | nl | | | nl-BE | | | pl | | | pt | | | pt-PT | | | sv | | | tr | | ----- ## 構造化データ