Skip to content
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

Closed
QA1MTG opened this issue May 3, 2018 · 18 comments
Closed

captureEntirePageScreenshot command is not available #182

QA1MTG opened this issue May 3, 2018 · 18 comments

Comments

@QA1MTG
Copy link

QA1MTG commented May 3, 2018

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?

@corevo
Copy link
Member

corevo commented May 3, 2018 via email

@QA1MTG
Copy link
Author

QA1MTG commented May 3, 2018

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)

@corevo
Copy link
Member

corevo commented May 3, 2018

No limits on any number of screenshots I was thinking a command like so
takeScreenshot | name of screenshot | format.
This gives the most flexibility imo.

I'll answer the curiosity in the other issue, where it's more relevant.

@QA1MTG
Copy link
Author

QA1MTG commented May 3, 2018

thanks. as long as I can access that screenshot and use it for the PDF docs when I need that would be perfect.

@QA1MTG
Copy link
Author

QA1MTG commented Jun 24, 2018

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.

@corevo
Copy link
Member

corevo commented Jun 25, 2018

We have just released a plugin system, I can't give you an ETA on when we'll ship something like this.
But it is absolutely possible to use this plugin system for that.

@idefix1
Copy link

idefix1 commented Jun 26, 2018

Just as a pointer: The kantu ide supports captureEntirePageScreenshot. It stores the screenshots in the browser local storage (and can export them).

But it is absolutely possible to use this plugin system for that.

Not me, but maybe someone that knows more about Javascript can write a plugin ;)

@QA1MTG
Copy link
Author

QA1MTG commented Sep 21, 2018

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?

@corevo
Copy link
Member

corevo commented Sep 21, 2018

Selenium is an opensource project, and as such work on community issues is based on contributors free time.
The project does not give timeframes on any pending ticket, if it is highly urgent, I suggest sending a pr.

@dmitrymurashenkov
Copy link

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.

@valentfj
Copy link

valentfj commented Jan 27, 2019 via email

@bugb
Copy link

bugb commented Jan 28, 2019

The captureEntirePageScreenshot feature would be great!

@cnrun
Copy link

cnrun commented Apr 29, 2019

+1

@digital-soul18
Copy link

++++1

Would really love to see this ... I can't find it in the latest IDE

@stale stale bot added the stale label Sep 2, 2019
@SeleniumHQ SeleniumHQ deleted a comment from stale bot Sep 2, 2019
@tourdedave tourdedave removed the stale label Sep 2, 2019
@wagnerteixeira
Copy link

+1

1 similar comment
@mortezaalizadeh
Copy link

+1

@tourdedave
Copy link
Contributor

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.

@SeleniumHQ SeleniumHQ locked as resolved and limited conversation to collaborators Apr 7, 2020
@toddtarsi
Copy link
Contributor

Closing this, if anyone needs this on v4 they can raise a new issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests