luke's blog

Screenshot Comparison API released

We've released a new API for calling our Screenshot Comparison process and retrieving layout differences programmatically. Many of our customers have asked for programmatic access to these results outside of the UI. We've also added some additional functionality such that users can now call comparisons against any two screenshots from any of their tests, or compare an older test to a newer one in parallel for regression testing.

To learn about the API and begin implementing it into your work flow, see the Comparison API documentation

Cancel Active Screenshots

We have had many users ask us for the ability to cancel screenshots single or for a whole test they just started. Today, we added this ability to the screenshot service, both in the UI and via our Screenshot API .

CANCEL SINGLE SCREENSHOT: When using our app, users can now hover over a single screenshot that is running and click the "cancel" button to stop the execution of the one browser test.

Opera 26+ enabled for desktop screenshots

Today we released Opera 26 and 27 screenshots across Windows and Mac OS.

Up until now, Opera browsers were only supported for versions 11 and 12 by Selenium's browser-automation tool, hence those were the only ones we could offer for screenshots. Selenium support starts with version 26, therefore we are offering these two latest versions with our screenshot system.

Opera moved from their Presto-based browser engine to Chromium starting with version 15. There are no 13 and 14 versions of Opera.

Paste via CMD/CTRL+V added to HTML5 client

Those of use that use our keyboards to quickly copy and paste text may have found the fact that you could not paste into a Live Test session a little limiting. Though we do offer a Send Text input field in the app, this requires extra clicks and can be a bit slow.

To address this issue with the HTML5 client, we added the ability to paste clipboard data from your local machine into a Live Test session.

Added 'Hide Fixed Elements' for Improved Fullpage Screenshots

We added a new feature to Screenshots for fullpage results that hides fixed-position elements appropriately. This makes it easier to visually verify layout down the fully-scrolled web page when fixed elements are not blocking the view.

Read more and see an example in our FAQ.

API Version 2.0 Released

Now there's a new version of the API! We have taken in your suggestions, as well as attempted to more closely mirror the functionality of our web interface. View Documentation
What's new in this version:

Layout Comparisons for Screenshots - Beta!

Today we are pleased to release an addition to our automated screenshots system which offers the ability to compare and detect layout differences between browsers. This tool not only visually indicates where layout differences occur against a screenshot image but gives you the ability to see your web page renderings side-by-side, enabling you to find discrepancies more effectively.

Layout Comparison Page Example

Improved Screenshot Viewing

Today we've added a "lightbox" control to quickly view and navigate through each screenshot image on the results page. This removes the "Layout" choices for small, medium, and large which are no longer necessary. Now when you want to see the large scale result of your screenshot, you no longer have to click into another page, or change the layout and scroll down the page. We think this will make reviewing your screenshot results much simpler!

Improved screenshot view example

Improvements to Screenshot Test Results Page

We've added a couple of enhancements to our screenshot test results page that we think you'll find very useful!

As our screenshot engine processes a requested browser, the "windowed" screenshot is returned to the results page as soon as it's complete, meaning, screenshot images start appearing on the screen more quickly. Also, if the "fullpage" version fails for any reason, the "windowed" result is still available for review. In the case of a failure, your time will not be deducted against, so the "windowed" screenshot is on us.

Added URL check for HTTP Status on Screenshot Test launch page

In the past, we've noticed users running screenshot tests on pages that have issues being loaded in the requested browser. This then causes either failed screenshot results, or a screenshot of the browser showing the page could not be loaded for one reason or another.

Syndicate content