New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
captureEntirePageScreenshot command is not available #182
Comments
Taking screenshots is not a problem.
The problem is that other than downloading them we can't save them.
Much like the way when you save the project it downloads instead.
Would downloading screenshots suffice?
Cheers,
Tom
…On 3 May 2018, 18:00 +0300, QA1MTG ***@***.***>, wrote:
My automation testing relies heavily on screenshot generation as a part of our testing capabilities. Currently it's not available. Is there an alternative or will this feature be added in?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Thanks for answering these so quickly. This has been really helpful. When I execute the old screenshot command, the screenshots are saved locally and then we make PDFs to distribute to our teams. It's been a real vital part of our testing strategy, and it's helped us quickly establish visual coverage of our systems. If it's automatically making screenshots and downloading them, how would the mechanism work? Would the screenshots be automatically numbered? Would there be a limit to the number of screenshots made? Is there a reason the old command can't be added back (just asking out of curiosity) |
No limits on any number of screenshots I was thinking a command like so I'll answer the curiosity in the other issue, where it's more relevant. |
thanks. as long as I can access that screenshot and use it for the PDF docs when I need that would be perfect. |
Hi. Is there an ETA on the screenshot functionality? My organization and I depend on using the screenshots for visual confirmation of functionality, and it's one of the features preventing me from upgrading to new Selenium. |
We have just released a plugin system, I can't give you an ETA on when we'll ship something like this. |
Just as a pointer: The kantu ide supports captureEntirePageScreenshot. It stores the screenshots in the browser local storage (and can export them).
Not me, but maybe someone that knows more about Javascript can write a plugin ;) |
Hi. Just a follow up regarding the request for screenshots. In most of my suites we rely on screenshots to help with verification. Is there a timeframe to have this added to selenium IDE? |
Selenium is an opensource project, and as such work on community issues is based on contributors free time. |
I'd like to describe case we have in our company that may help shape this feature. In our company Selenium IDE is used by manual QA testers who often have troubles adding any verification logic, even basic one. Second point is that many bugs we face are problems with html layout and can't be automatically verified easily. So we rely on screenshots. A nice feature would be to have a "screenshots log" like Katalon Recorder for Chrome does. So you run tests and then manually go through all screenshots to check that everything looks okay. Although not fully automated, it saves a lot of time when a single test case requires filling 20 forms with 10 fields each. Perhaps screenshot command should take an optional "comment" argument to describe expected state for manual verification like "shopping cart should have 2 products in it", so that newcomer tester can quickly check if screenshot shows correct state. |
Great idea
…Sent from my iPhone
On Jan 27, 2019, at 11:38 AM, Dmitry Murashenkov ***@***.***> wrote:
I'd like to describe case we have in our company that may help shape this feature.
In our company Selenium IDE is used by manual QA testers who often have troubles adding any verification logic, even basic one. Second point is that many bugs we face are problems with html layout and can't be automatically verified easily. So we rely on screenshots.
A nice feature would be to have a "screenshots log" like Katalon Recorder for Chrome does. So you run tests and then manually go through all screenshots to check that everything looks okay. Although not fully automated, it saves a lot of time when a single test case requires filling 20 forms with 10 fields each.
Perhaps screenshot command should take an optional "comment" argument to describe expected state for manual verification like "shopping cart should have 2 products in it", so that newcomer tester can quickly check if screenshot shows correct state.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
The captureEntirePageScreenshot feature would be great! |
+1 |
++++1 Would really love to see this ... I can't find it in the latest IDE |
+1 |
1 similar comment
+1 |
Appreciate the interest on getting the feature added. There's currently no ETA for adding it. If someone wants to contribute a PR to add it we will happily accept it. |
Closing this, if anyone needs this on v4 they can raise a new issue. |
My automation testing relies heavily on screenshot generation as a part of our testing capabilities. Currently it's not available. Is there an alternative or will this feature be added in?
The text was updated successfully, but these errors were encountered: