Exploratory Testing Extension
Chrome extension for exploratory testing
Now everyone on the team can own quality. Capture findings, create issues, and collaborate with the team, directly from the browser.
按已采集快照查看用户数变化。
展示最近 7 日窗口内已采集的评分快照,辅助判断近期评分是否稳定。
同口径展示 1 天、7 天、30 天的绝对增长与增长率。
查看发布时间、版本、支持语言、最近更新和抓取时间。
查看插件说明、主要功能和适用场景。
Test & Feedback - Now everyone on the team can own quality. Capture findings, create issues, and collaborate with the team, directly from the browser.
Everyone in the team, be it product owners, developers, testers, UX designers etc., can now test their web-apps and give feedback, all directly from the browser on any platform: Windows, Mac, or Linux. All kinds of teams will now be able to drive quality in 3 easy steps – capture, create & collaborate.
Capture - Take notes, screenshots with annotations, and screen recordings to capture problems. Automatically include rich data like user actions (as an image action log), page load data, and system information.
Create - Create bugs, tasks, and feedback response work items to send feedback or report problems. Create test cases quickly based on the image action log while you explore your app. Automatically attach all your captured information.
Collaborate - Work offline in standalone mode, then export your session to share findings with your team. For more integrated experiences with end-to-end traceability, connect to Azure DevOps Services or to Team Foundation Server 2015 or later. For example, you can explore user stories directly from the board, manage all feedback requests received, and easily track bugs, tasks and other work-items. To view completed exploratory sessions and get insights across all completed sessions, for example, details about sessions and work items that are created, explored, and weren’t explored, plus other data, go to your exploratory testing insights page.
You can use the extension for FREE in these modes: Standalone and Connected
查看最近评论和评分分布。
商店综合星级:4.2。下方星级分布只统计已同步评论正文;如果某个插件只有公开分数、没有真实评论正文,这里可能为空。
查看 Chrome 商店详情页中的相关产品。
Chrome extension for exploratory testing
Click on any element to get the xPath
Arineo Table browser caller for Microsoft Dynamics 365 for Finance and Operations.
Right-click context menu to help with exploratory testing
Accessibility Checker for Developers, Testers, and Designers in Chrome
TestCase Studio record the user actions performed on a web application in English Sentences. Best alternative for Selenium IDE
This has great potential but there are a few setbacks. The main one for me right now is that I want to link a recording to a test case. It will only allow us to view the recording if we create a task or bug. It doesn't allow us to export from a session or even record in standalone mode. Cannot find any reason for it. This is a bummer because that recording would make a difference.
Still broken
I have been using this extension for a long time, noticed a problem in the new release version 1.0.246.0. Below are the steps to reproduce this issue. - Right click on the browser extension icon - Select "Options" - In the Options window, change "Number of most recent events to record (Maximum 200)". The default value is 15. Change it to any other number. Then close the Options window. - The new change does not reflect. Number is still 15. =========== Update: This is still broken in version 1.0.247.0 =========== Thanks for responding - When can we expect the next release? =========== Update: This is still broken in version 1.0.254.0. The max value can change now, but the test case / bug created in ADO only has 15 steps. Why can't we get a bug fix for a feature that was WORKING?
excelente
nice
Trying to connect to Microsoft hosted Azure Devops and it says I need to be using a version >= TFS 2015. Doesn't work.
Es muy útil y practico, me gusta
Is this a supported extension? The last update is over a year ago and the how-to video's gone. I'm trying it because it would help make posting issue info very nice. The screenshots and session info are uploaded to the issue, but I don't see the video capture or notes submitted to Azure DevOps. I see there's difference in access for basic and stakeholder, but this doesn't seem to be one of them. What am I missing?
The idea is excellent!, could be useful to attach a file for a Bug/Task
useless if you have testcases with more than 15 steps, would be pretty useful otherwise