Changelog

August 22nd, 2023

  • It is now possible to add comments to a result or suite result via the API

July 14th, 2023

  • The "Chrome (Latest Version)" option has been upgraded to v114
  • The "Firefox (Latest Version)" option has been upgraded to v114
  • The variables page will now paginate for organizations with large numbers of variables.

July 4th, 2023

  • The Accessiblity testing library (axe-core) as been updated to version 4.7.2.

May 19th, 2023

  • The "Chrome (Latest Version)" option has been upgraded to v113
  • The "Firefox (Latest Version)" option has been upgraded to v113

March 28th, 2023

  • Our browser extension was upgraded to Manifest v3.

March 27th, 2023

March 21st, 2023

February 17th, 2023

  • Upgrade Faker library to version 7.

February 1st, 2023

November 6th, 2022

  • The "Chrome (Latest Version)" option has been upgraded to v107
  • The "Firefox (Latest Version)" option has been upgraded to v106

September 15th, 2022

  • The "Chrome (Latest Version)" option has been upgraded to v105
  • The "Firefox (Latest Version)" option has been upgraded to v104

July 5th, 2022

June 15th, 2022

  • The "Chrome (Latest Version)" option has been upgraded to v102
  • The "Firefox (Latest Version)" option has been upgraded to v101

May 12th, 2022

  • The "Chrome (Latest Version)" option has been upgraded to v101
  • The "Firefox (Latest Version)" option has been upgraded to v100

March 25th, 2022

  • The "Chrome (Latest Version)" option has been upgraded to v99
  • The "Firefox (Latest Version)" option has been upgraded to v98

February 23rd, 2022

  • Notification issues (such as a missing Slack channel or a webhook URL error) are now recorded and displayed on test and suite screens.
  • An alert is displayed when a test run was unable to find the element specified as the screenshot target at the end of the test. The test falls back to a full page screenshot in this scenario.
  • We've extended the maximum runtime of an entire suite from 8 hours to 12 hours and display this limit in the concurrency settings.

February 17th, 2022

  • The "Chrome (Latest Version)" option has been upgraded to v98
  • The "Firefox (Latest Version)" option has been upgraded to v97
  • Axe library has been updated to v4.4 with additional accessibility testing rules
  • Browser versions prior to Chrome v89 and Firefox v88 have been removed

January 13th, 2022

  • Released our Jira integration which adds the ability to create Jira issues from failed tests and execute tests from within Jira.
  • The "Chrome (Latest Version)" option has been upgraded to v97
  • The "Firefox (Latest Version)" option has been upgraded to v96

January 11th, 2022

  • Added an API endpoint for getting an organization
  • Added the ability to sort organization and suite variables by date or name
  • Added a warning when an organization or suite variable name is a duplicate
  • Added the ability to download a Data Source as CSV

December 28th, 2021

  • Keypress steps now support the use of "Shift", "Control" and "Alt" modifier keys
  • Keypress steps now support the use of "Home" and "End" keys

December 23rd, 2021

  • The application’s favicon will now reflect the status of the suite, test or result you are viewing using a colored dot in the lower right corner.
  • When viewing a test result, the "View Options" menu now includes an "Hide skipped steps" option which will hide all steps that were skipped during execution of the result due to a step condition returning a falsy value.

December 21st, 2021

  • Runtime variables are now available during test execution, giving you access to the current result at runtime.

December 2nd, 2021

  • The "Chrome (Latest Version)" option has been upgraded to v96
  • The "Firefox (Latest Version)" option has been upgraded to v94

November 2nd, 2021

  • The "Chrome (Latest Version)" option has been upgraded to v95
  • The "Firefox (Latest Version)" option has been upgraded to v93

September 22nd, 2021

  • Released version 6.1.0 of our web test recorder which includes:
    • adds the ability to add accessibility testing steps while recording tests
    • adds the ability to add screenshot capture steps while recording
    • various bug fixes and UI design improvements

September 13th, 2021

  • The "Chrome (Latest Version)" option has been upgraded to v93
  • The "Firefox (Latest Version)" option has been upgraded to v92

August 23rd, 2021

  • "Check Accessiblity" steps now include all iframes on the page when checking for accessibility issues.

August 5th, 2021

  • The "Chrome (Latest Version)" option has been upgraded to v92
  • The "Firefox (Latest Version)" option has been upgraded to v90

July 27th, 2021

  • Added API parameter dataSource which can be used to pass the ID of the Data Source you wish to use during test or suite execution.

July 22nd, 2021

  • New screenshot baselines can now be accepted directly on test result pages (in addition to the test’s index page).

June 20th, 2021

  • Added the ability to specify a delay (in milliseconds) when executing tests or suites via the API, up to a maximum of 5 minutes.

June 3rd, 2021

  • The "Chrome (Latest Version)" option has been upgraded to v91
  • The "Firefox (Latest Version)" option has been upgraded to v89
  • The OS used for browser execution was updated. In rare situations this may have caused slight differences in font rendering for older browser versions that could have caused one-time screenshot comparison failures.

May 24th, 2021

  • Released our official Netlify plugin for automatically triggering tests on deploy.

May 10th, 2021

May 5th, 2021

April 27th, 2021

April 21st, 2021

  • The "Chrome (Latest Version)" option has been upgraded to v90
  • The "Firefox (Latest Version)" option has been upgraded to v88

April 12th, 2021

April 6th, 2021

  • Released version 6.0 of our web test recorder which includes our new design and usability improvements

April 5th, 2021

March 22nd, 2021

  • Variables are now included as columns in test run history CSV exports
  • Released v3.2 of our Jenkins plugin with the following improvements:
    • Support for running multiple suites in a single build step
    • Support for suites run with data sources
    • Improved handling of error responses
  • Added the ability to use variables within Slack channel setting.
  • Add the ability to bundle imported steps when exporting tests or suites in JSON format.

March 11th, 2021

  • Our official Microsoft Teams integration is now available
  • Released version 5.4.3 of our recording extension which includes improvements to the selector generator logic and better use of custom attributes
  • The "Chrome (Latest Version)" option has been upgraded to v89
  • The "Firefox (Latest Version)" option has been upgraded to v86

March 10th, 2021

  • Application redesign improvments:
    • Added a "Layout mode" setting with a full-width mode to use all available viewport space
    • Improved readability of step statuses in results with additional colors and borders for failing steps
    • Added a new "# in-progress" indicator to the sticky header of the suite and test screens when scrolling
    • Various spacing and layout adjustments

March 3rd, 2021

  • Brand new design for both website and application. We introduced lots of usability and accessibility improvements with more on the way.

February 19th, 2021

  • The test execution API endpoint now allows the screenshot comparison baseline to be overridden with any completed test result in your organization using the screenshotCompareBaselineResult parameter.

January 26th, 2021

  • The “Chrome (Latest Version)” option has been upgraded to v88
  • The “Firefox (Latest Version)” option has been upgraded to v84

January 19th, 2021

  • Released version 5.4.1 of our recording extension which includes these changes:
    • adds keyboard shortcuts to switch between operation (Alt + O) and assertion (Alt + A) mode
    • fixes bug where an empty <div> was being added to text editors like CKEditor

December 17th, 2020

  • The API response for /api/suites/xxx/execute has been changed when using immediate=0 and executing multiple suites (via Data Source, CSV, etc). The API response will now return a list of suite results instead of a list of test results.

November 24th, 2020

  • The “Chrome (Latest Version)” option has been upgraded to v87
  • The “Firefox (Latest Version)” option has been upgraded to v83

October 20th, 2020

  • Deleted suites and tests are now moved to the Recycling Bin (in organization settings). They can be restored within 30 days, after which they will be permanently deleted.

October 13th, 2020

  • The “Chrome (Latest Version)” option has been upgraded to v86
  • The “Firefox (Latest Version)” option has been upgraded to v81

September 28th, 2020

  • On-demand tests will now accept a test _id which, when provided, will link results back to the specified test within your account.

September 3rd, 2020

August 31st, 2020

  • Tests can now be marked as “Import Only” in Settings > Modularization. Enabling this option will prevent the test from being run directly and hide a number of settings that are no longer applicable. It will also purge all previous results and reset the test’s statuses.

August 27th, 2020

  • The “Chrome (Latest Version)” option has been upgraded to v85
  • The “Firefox (Latest Version)” option has been upgraded to v80
  • We have added an endpoint to our API that publishes our test runner IP addresses by region.

August 26th, 2020

  • “Element is not present” assertions will now check all open windows and tabs to ensure that the element is not present anywhere. Previously this assertion only checked the active window.
  • Organization variables are now applied to on-demand tests.
  • On-demand tests now accept the autoRetry parameter and will attempt to retry the test on failure when true.

August 25th, 2020

  • CSV files can now be uploaded and saved as Data Sources for data-driven execution of tests and suites, including on a schedule.
  • Added the ability to specify Data Concurrency which will limit the number of rows executed simultaneously when executing with a CSV or Data Source.

July 16th, 2020

  • The “Chrome (Latest Version)” option has been upgraded to v84
  • The “Firefox (Latest Version)” option has been upgraded to v78

July 14th, 2020

  • Released version 5.3.2 of our recording extension which adds the ability to customize your preferred selectors (e.g. data-test). After updating, click the gear icon to change your settings.

June 29th, 2020

  • Released v3.0 of our Jenkins plugin with the following improvements:
    • Compatibility with Jenkins v2.235.1 and above
    • Increased build step timeout from 1 hour to 10 hours
    • Environment variables are now replaced in all build step configuration parameters

June 23rd, 2020

June 17th, 2020

June 4th, 2020

  • The “Chrome (Latest Version)” option has been upgraded to v83
  • The “Firefox (Latest Version)” option has been upgraded to v77

May 28th, 2020

  • Released version 5.3.1 of our recording extension which includes:
    • Selector logic improvements will make use of title, placeholder and for attributes
    • Selector logic improvements will make use of data-testid and data-test-id attributes
    • Fixed issue where class exclusions were not being honored which lead to undesired class names (such as ng-*) being captured in selectors

May 20th, 2020

  • The Advanced Schedule feature can now schedule tests and suites to run at any chosen minute(s) of the day. (Previously only :00, :15, :30 and 0:45 were supported.)

May 11th, 2020

May 6th, 2020

  • You can now update a test using our API. Note: Previously it was possible (though undocumented) to use a POST request when accessing the get test endpoint. That is no longer supported. A GET request must be used when fetching a single test.

May 4th, 2020

  • You can now update a folder using our API. Note: Previously it was possible (though undocumented) to use a POST request when accessing the get folder endpoint. That is no longer supported. A GET request must be used when fetching a single folder.

May 1st, 2020

  • You can now create a folder using our API. Note: Previously it was possible (though undocumented) to use a POST request when accessing the get folder endpoint. That is no longer supported. A GET request must be used when fetching a single folder.

  • An organization ID is now required in the POST body when using our API to create a suite.

April 28th, 2020

  • We have adjusted the way “nested” Conditions work. Previously, each step was only capable of checking a single condition. When a condition was applied to an “Import Steps from Test” step, it would override all conditions in the imported steps. We have adjusted this behavior so that conditions used on “Import Steps from Test” steps will be combined with any conditions on the imported steps themselves. This means that steps can accumulate multiple conditions when conditions are being applied to multiple levels of imports. The conditions will be effectively AND’ed together. Each condition will be checked in order. The step will be executed only if all conditions return truthy values.

April 24th, 2020

  • You can now update a suite using our API. Note: Previously it was possible (though undocumented) to use a POST request when accessing the get suite endpoint. That is no longer supported. A GET request must be used when fetching a single suite.

April 21st, 2020

  • You can now create a suite using our API. Note: Previously it was possible (though undocumented) to use a POST request when accessing the suite listing endpoint. That is no longer supported. A GET request must be used when fetching the suite listing.

April 20th, 2020

  • Released version 5.3.0 of our recording extension which adds the ability to log into the extension via the web application (SSO supported)

April 14th, 2020

  • The “Chrome (Latest Version)” option has been upgraded to v81
  • The “Firefox (Latest Version)” option has been upgraded to v75
  • Test editor step numbering is now automatically adjusted to account for steps from imported tests
  • Added ability to copy selectors and values to the clipboard by clicking on them while viewing a test result

April 2nd, 2020

  • Sign Sign-On (SSO) is now available on our enterprise plans

March 30th, 2020

  • The “Firefox (Latest Version)” option has been upgraded to v74

March 12th, 2020

  • Added a public API endpoint for getting currently running results for all tests belonging to an organization.

February 11th, 2020

  • The “Chrome (Latest Version)” option has been upgraded to v80

February 3rd, 2020

  • On-demand tests now have the ability to import tests using the execute command.

January 31st, 2020

  • Released version 5.2.2 of our recording extension, which adds support for using data-testing, data-test and data-qa attributes for element selectors.

January 29th, 2020

  • Added notification “Threshold” setting to PagerDuty integrations.
  • Added support for variables in webhooks URLs.

January 27th, 2020

  • Re-branded extension from "VSTS" to "Azure DevOps" to match the updated Microsoft naming (published version 1.0.9).

January 22nd, 2020

  • Added option to include only failed test results in Slack suite notifications.
  • Added option to include test result start URLs in Slack suite notifications.

January 20th, 2020

  • Added notification “Threshold” setting; This controls whether a notification is sent immediately upon failure, or only after X failures occur.
  • Added notification option “Send every time the test or suite fails” (without a passing notification afterwards).

January 14th, 2020

  • The “Firefox (Latest Version)” option has been upgraded to v72
  • The firefox value of the browser parameter in the API will now track the latest version of Firefox (instead of the legacy version)

January 13th, 2020

  • Regular Expressions are now supported in text assertions. The standard JavaScript /pattern/ syntax can be used in step values of text assertion step to match element text.
  • Added Go back step action for navigating back a page during a test. This is equivalent to clicking “Back“ in the browser.
  • Added the ability to trigger webhooks for passing or failing test results only.
  • Added a “Language” setting under Browser Access to control the language specified by the browser. This corresponds to the Accept-Language header that the browser includes in HTTP requests.
  • Added an “SSL Certificates” setting under Miscellaneous to control whether a test’s browser should accept or reject invalid SSL certificates. The system accepts them by default.
  • Improvements to the Screenshot Exclusions logic help ensure that all nested elements (inside of the excluded element) are hidden properly.
  • Test alert emails have been updated to include both new and baseline screenshots when the screenshot comparison fails.

December 17th, 2019

  • The “Chrome (Latest Version)” option has been upgraded to v79
  • The “Firefox (Latest Version)” option has been upgraded to v71

December 5th, 2019

  • We’ve added an “Exit Test” step action that allows you to exit a test run early with a passing or failing status. Conditions can be applied to the step to perform the exit under certain circumstances only.

December 4th, 2019

  • Added an option to Collapse Imported Steps when viewing test results, making it easier to read through tests with many modular sections.

November 4th, 2019

  • We’ve added the ability to search your account, making it easier to find your folders, suites, tests, variables, and steps.

November 1st, 2019

October 29th, 2019

  • The “Chrome (Latest Version)” option has been upgraded to v78

October 8th, 2019

October 2nd, 2019

  • The “Chrome (Latest Version)” option has been upgraded to v77

September 23rd, 2019

  • Users can now add backup selectors to test steps that utilize a CSS or XPath target.
  • Full-length screenshot logic has been improved to help ensure the full page is captured and scrollbars are avoided. Note that this may trigger one-time screenshot failures for pages with variable length and/or sensitive tolerances.

September 17th, 2019

September 16th, 2019

  • Step timing settings can now be controlled for all tests in a suite under Settings > Test Defaults. Existing tests with unmodified timing settings have been updated to default to the suite’s settings.

September 9th, 2019

  • The “Chrome (Latest Version)” option has been upgraded to v76
  • Drag-and-drop steps now offer a “Simulated” option (in addition to “Native”) which may perform better in certain scenarios

September 5th, 2019

  • Printer-friendly stylesheet enhancements for cleaner printing and PDF exporting of test results

August 13th, 2019

  • Variables provided to a test result are now viewable in the new “Variables” section below the test steps (collapsed by default).

August 12th, 2019

  • Screenshot steps without a target selector will now capture a full-height screenshot of the page, instead of a viewport-sized screenshot.

August 8th, 2019

  • Folders have been added to the navigation breadcrumbs. Clicking on a folder name in the breadcrumbs will take you to a page listing all the suites within that folder and allow you to rename or delete the folder.

August 6th, 2019

August 1st, 2019

  • Screenshot steps can now target specific elements on the page and capture an image of that element only

July 24th, 2019

  • Test results with video enabled will now display the corresponding step numbers in an overlay on the video
  • Released version 5.1.0 of our recording extension, which adds two-factor authentication to the login if enabled for your account

July 16th, 2019

  • A number of test runner changes have been made as outlined in our Browser & System Updates — July 2019 blog post
  • The “Chrome (Latest Version)” option has been upgraded to v75
  • Firefox versions v66 and v67 are now available
  • Large speed improvements when interacting with multiple tabs or popup windows
  • Improved drag-and-drop support
  • Screenshot targets are now supported in Chrome
  • Firefox can now accept unsigned/invalid SSL certificates
  • Assignments can now be made to <select> elements by specifying the option’s index as index=# in the step
  • All tests will have automatic access to a {{startUrl}} variable containing the start URL of the test run

July 15th, 2019

  • Added ability to easily re-trigger a test using the settings from a previous result

June 27th, 2019

June 12th, 2019

  • Dark mode is now available in the application. It can be enabled in account settings.
  • Added more screen size options for tests. The default screen size is now 1280x800.

June 10th, 2019

  • Added the ability to see where a test is being imported under Settings > Miscellaneous

April 17th, 2019

  • Released version 5.0.6 recording extension, which adds the option (in settings) to assert element visibility instead of presence, fixes a bug with the default ignored classes, and improves error handling.

April 2nd, 2019

  • Released the initial version of our WordPress Plugin, which allows you to view Ghost Inspector test results in your WordPress.org admin dashboard (read more).

March 25th, 2019

  • Added page size options for test result and suite result listings
  • Added bulk delete options for test results and suite results
  • Added CSV download feature for suite results

March 18th, 2019

  • When a text assertion fails, the text that was found on the page is now captured and displayed with the test step in the result.
  • Visual capture (of screenshots and video) can now be disabled for tests under Settings > Display Options, or Settings > Test Defaults for the whole suite.

March 11th, 2019

  • Added External Links to test settings, which adds the ability to associate a test with a Jira issue (or anything else with a permanent URL).

March 5th, 2019

  • Added endpoint to get a list of all running instances of a test through the API.

March 4th, 2019

  • Added the ability to accept a screenshot for a test through the API.
  • Released version 5.0 of our recording extension, which adds the ability to save new suites, an option to default to the suite start URL, and insert recordings after a specific step of an existing test.

February 6th, 2019

February 4th, 2019

  • Chrome versions v71 and v72 are now available
  • The “Chrome (Latest Version)” option has been upgraded to v72
  • Added geolocation option for Stockholm, Sweden. The new IP addresses can be found on our Test Running Service IP Addresses page.

February 1st, 2019

  • Added export option for the new Selenium IDE extension (in .side format).

January 14th, 2019

  • Added additional key options to the “Keypress” step action.

December 3rd, 2018

  • Added the ability to comment on suite and single test results.

November 13th, 2018

  • The “Chrome (Latest Version)” option has been upgraded from v69 to v70
  • We are now maintaining options for older versions of Chrome (v68+)

November 7th, 2018

October 23rd, 2018

  • Test result email notifications have been updated to include browser, screen size, geolocation and duration.

October 18rd, 2018

October 4rd, 2018

October 3rd, 2018

  • Suite results can now be pulled in XUnit v2 format via the API.
  • Added ability to run asynchonous JavaScript steps.

September 28th, 2018

  • Added the ability to run tests with previous versions of Chrome, starting with v68.

September 19th, 2018

  • The “Firefox (Latest Version)” option has been upgraded from v59 to v60
  • Added alphanumeric key options in “Keypress” steps

September 13th, 2018

  • The “Chrome (Latest Version)” option has been upgraded from v68 to v69
  • Firefox v60 is now available as a browser option. The “Firefox (Latest Version)” option will remain on v59 for a short time before the switch to v60 is made.
  • Improved keypress event accuracy during Firefox automation
  • Added “Space” as a key option in “Keypress” steps
  • Converted folder and suite dropdown menus to Select2 menus for easier searching and selection

August 2nd, 2018

  • The “Chrome (Latest Version)” option has been upgraded from v67 to v68.

August 1st, 2018

  • Tests and suites now have the ability to enable public status badges (disabled by default) under Settings > Details > Enable Status Badge. Status badges are embeddable in SVG format via the API

July 9th, 2018

  • We’ve added the ability to persist variables between test runs when running a suite sequentially. This can be enabled under Suite > Settings > Concurrency when concurrency is set to 1. When this option is enabled, all variables will be passed on to the next test run as the suite progresses.

July 3rd, 2018

  • Allow suites to be drag-and-dropped into (and out of) folders on the dashboard

June 29th, 2018

  • Released Node.js API package version 3.0.0 with support for additional API endpoints.
  • Released Grunt Plugin version 2.0.0 with updated dependencies.
  • Fix “Edit” links in steps that are imported from tests multiple levels deep.
  • Allow steps to be dragged (reordered) above or below the viewing window in test editor.

May 31st, 2018

  • The “Chrome (Latest Version)” option has been upgraded from v65 to v67.
  • There is a now an “Every 10 minutes” scheduling option available for paid plans.
  • Lots of application usability improvements including sticky sidebar panels, additional labels, and table row highlighting.

May 9th, 2018

  • You can now add folders to your dashboard for grouping your suites together.
  • The dashboard display has been updated for more clarity into test statuses.

May 1st, 2018

April 12th, 2018

March 19th, 2018

  • Options for customizing browser and screen size have been added to the “Run w/Custom Settings” dialog.

March 16th, 2018

  • The test result CSV export button now exports the latest 1,000 results (instead of just 100).
  • The test result CSV export now includes a column with the ending URL of the test result.

March 15th, 2018

  • The “Chrome (Latest Version)” option has been upgraded from v64 to v65.
  • The “Firefox (Latest Version)” option has been upgraded from v58 to v59.

February 14th, 2018

  • The test editor now incorporates a JavaScript code editor for JavaScript steps.
  • Syntax highlighting has been added to JavaScript steps in the test result display.

February 6th, 2018

  • There are now two options for selecting failing tests within a suite, Select Failing Steps and Select All Failing Tests.
  • Test runs will now fail explicitly when an imported test is missing.
  • browser can now be specified as a parameter for test execute and suite execute API calls.
  • Our Jenkins plugin has been updated to v1.2. It adds the ability to pass custom parameters to the API and also popuplates environment variables within the start URL and parameters.

February 2nd, 2018

  • Our Jenkins plugin has been updated to v1.1. It includes improvements for dealing with long running suites.
  • Add new HD viewPort size of 1920x1080 for all paid plans.

January 30th, 2018

  • The “Chrome (Latest Version)” option has been upgraded from v63 to v64.
  • The “Firefox (Latest Version)” option has been upgraded from v57 to v58.

January 26th, 2018

December 20th, 2017

  • Added new geolocation in Paris, France
  • Variables can now be used in HTTP authentication credentials

December 7th, 2017

  • The “Chrome (Latest Version)” option has been upgraded from v62 to v63.
  • Chrome now captures full page screenshots at the end of each test.

November 28th, 2017

  • The “Firefox (Latest Version)” option has been upgraded from v55 to v57.

November 21st, 2017

  • Added Firefox versions 56 and 57

November 7th, 2017

  • Added duplicate test functionality to the API.
  • Added duplicate suite functionality to the API.

October 18th, 2017

  • The latest version of Chrome has been upgraded from v61 to v62.
  • The latest version of Firefox has been upgraded from v52 to v55.

October 9th, 2017

  • Added formal GitHub integration for sending commit statuses back to GitHub when tests and suites triggered via webhooks
  • Added Firefox versions 53, 54 and 55

September 14th, 2017

  • Convert “Import Steps” dropdown menu to searchable typeahead widget for faster and easier selection of test imports in the test editor.

September 12th, 2017

  • The latest version of Chrome has been upgraded from v60 to v61.

September 5th, 2017

  • Our Chrome recording extension v4.0 has been released which includes the ability to record steps on to the end of existing tests.

August 9th, 2017

  • Firefox v45 has been upgraded to 45.9.0. Firefox v52 has been upgraded to 52.3.0.

August 8th, 2017

  • The latest version of Chrome has been upgraded from v59 to v60.

August 7th, 2017

  • Added API endpoints for canceling active suite and test runs.

June 19th, 2017

  • Organization-level variables can now be set using the “Variables” tab in your organization settings. These variables are available within all tests in your orgaization.
  • Improved accuracy when using the “Edit” links in the bottom, right corner of your test steps when viewing a result.
  • Added the ability to completely delete your Ghost Inspector account at the bottom of your account details screen.

June 13th, 2017

  • Chrome browser version has been upgraded from v58 to v59.

May 30th, 2017

  • Chrome (v58) is now available as a browser option in BETA form for all paid plans.

April 5th, 2017

  • Released official Jenkins plugin for Ghost Inspector.
  • Resolved issue where Command + A (Select All) was disabled in the test editor. It now works normally.
  • Upgraded Firefox v45.0.1 to v45.0.2 and v52.0 to v52.0.2.

April 2nd, 2017

  • The user who triggers a test or suite is now stored and displayed with the suite or test result in the application.
  • The start URL used for a suite run is now stored with the suite result and displayed in the application.

March 12th, 2017

  • Firefox v51 and v52 are now available as browser options.

March 6th, 2017

  • Active test and suite runs can now be canceled using the cancel buttons available in the application.
  • A confirmation dialog is now presented if you attempt to leave the test editor with unsaved changes.

February 27th, 2017

  • Variables can now be used in the names of suites and tests using our standard {{varName}} syntax. They will be replaced with the variables’ values upon execution.
  • CSV export options have been added for downloading test results from the test screen and the suite result screen.

February 6th, 2017

  • Added “Capture Screenshot” step action to premium plans so that screenshots can be captured throughout a test. The screenshots are included with results in both the application and email notifications.
  • Added options to “Click” command for right clicking and double clicking.
  • window.prompt() will now return the specified default value instead of null.

February 2nd, 2017

  • Improved support for HTML5 video playback in Firefox browser.

January 16th, 2017

  • Added the ability to export tests and suites in Selenium 2 (JSON) format (in addition to our existing HTML export option).
  • Added a dataFile parameter when executing tests and suites through the API which allows for a CSV file containing a row of variable values for each run as outlined in our data-driven testing section.

January 11th, 2017

  • New GhostInspector.com website design launched including improved docs, searching, and much more.

January 2nd, 2017

  • Added a “Copy” link above each test step in the test editor. “Paste” links will appear when a step is copied for easy duplication.

December 19th, 2016

  • Launched built-in email service for checking emails during test runs
  • Added test and suite details to notification emails
  • Increased maximum concurrency throttle from 20 tests to 50 tests

December 16th, 2016

  • Added the ability to view new screenshots and the baseline side-by-side
  • Improved coloring on screenshot comparison images
  • Added larger screen size options (up to 1600x1200) for paid accounts

December 14th, 2016

December 6th, 2016

  • Our screenshot comparison feature now maintains independent baseline screenshots for your test based on the settings for browser, screen size and geolocation. This means that you can trigger a test in various screen sizes, and each result will do an independent screenshot comparison against the baseline for that specific screen size. A baseline is maintained for every combination of browser, screen size and gelocation.

November 21st, 2016

  • Added Firefox 50.0 and upgraded Firefox 49.0.1 to 49.0.2
  • Suite and test screens in the application now refresh data in the background regularly
  • A “Start URL” column has been added to the test results table in large desktop view
  • Triggering a suite without any tests in it now results in an error

November 16th, 2016

  • When suite level variables use our built-in generators, consistent values are now generated for all tests in the suite run.

November 13th, 2016

  • Defaults can now be set for various display and miscellaneous options at the suite level under “Settings” > “Test Defaults”.
  • A comma-separated list of Slack channels can be specified for Slack notifications.

November 8th, 2016

  • Ability to choose options in <select> boxes using their label by prefixing value with “label=”.
  • Ability to specify custom HTTP headers used in the browser during your tests. These can be set at the suite level under “Settings” > “Test Defaults” and for individual tests under “Settings” > “Browser Access”.
  • Ability to upload a CSV spreadsheet file with rows of values corresponding to variables in your test(s). For each row, a test or suite run will be triggered using those variable values. This feature is available as “Run with Spreadsheet Data…” under the “More” dropdown menu in both suites and tests.

November 2nd, 2016

  • Element assertions have been updated to continue checking the condition you’ve specified for the “Element Timeout” period that’s been set for the test. Previously, element assertions would check the condition once, then immediately pass or fail. This update provides additional flexibility and control around elements that are created or changed over time (for example, a modal dialog that appears after 5 seconds).

October 26th, 2016

  • Assertions concerning element visibility will now factor in the “opacity” property. If the element being checked has an opacity of “0” it will be considered “not visible”. (All positive values above 0 will be considered visible.)

October 25th, 2016

  • Summary emails and Slack notifications can now be sent containing a full rundown of the test results from a suite run. The new “Suite Notifications” section is available above the existing “Test Notifications” section in the “Notifications” tab of organizations and suites.

October 18th, 2016

  • Added ability to specify variables when running a test or suite using the custom settings dialog
  • Added ability to fail a test run when a JavaScript error is encountered. This is available in a new “Miscellaneous” section in the test’s settings
  • Improved Slack notification messages with additional information

October 11th, 2016

  • JavaScript steps are now captured properly within the video of the result

October 10th, 2016

  • Added options for Firefox v46, v47, v48 and v49 to our system. You can also set your tests to always use the latest version of Firefox. (Due to rendering differences between v45 and v46, existing tests that were using the generic Firefox browser option have been left on v45 and can be adjusted manually.)

September 19th, 2016

  • Advanced scheduling options for tests and suites which allow you to run them on specific days and times during the week (Paid plans only)

September 12th, 2016

  • Ability to run tests from various geo-locations around the globe (Dublin, São Paulo, Sydney, Tokyo) is now available at the test and suite level

August 11th, 2016

  • Added the ability to run the same test or suite multiple times, concurrently. The “Run” button now remains enabled even when a run is in progress.
  • Added the ability to edit test steps and settings while an instance of the test is running
  • Added “Suite Results” which track suite runs and provide an overview and a listing of all the results
  • Added the ability to run a test suite in sequential order (1 test at a time) under Settings > Concurrency in the suite
  • Added the ability to limit suite runs to 1 - 20 concurrent tests (to help mitigate load issues on your server from many tests running) under Settings > Concurrency in the suite
  • A result record (with tracking ID) is now returned when tests and suites are triggered via the API with the “immediate” flag set
  • Runscope’s “Locations” feature can now be enabled on Runscope tests that integtrate Ghost Inspector tests

August 2nd, 2016

  • Our AWS CodePipeline integration now allows you to trigger full suites in your pipelines

July 19th, 2016

  • Suite name is now included in test alert emails
  • Added ability to edit 3rd party integration labels
  • Added billing period to line items in PDF invoices

July 18th, 2016

  • Screenshot statuses of tests are now shown on the dashboard (in addition to the normal test statuses)

June 27th, 2016

  • Uncaught exceptions are now captured and displayed in the console output section (in red) with a stack trace.
  • Long running JavaScript is now stopped after 10 seconds of uninterrupted execution to prevent infinite loops. (This is the same time limit used by most browsers to flag a page as unresponsive.)
  • Console log messages are now limited to 500 captures per test result (to prevent endless console logging).

June 14th, 2016

  • Added new "Mouse over" step command in the test editor for triggering “mouseover” events during tests.

May 13th, 2016

  • Added support for nested frames/iframes to both the recorder extension and the test running system.

April 28th, 2016

  • Added ability to define variables in suite settings which are available to all tests in the suite.
  • Added ability to accept (pass) failing screenshots for tests in bulk on the suite screen.
  • Added 1 minute test schedule.

April 21st, 2016

  • Added “Edit” links to each test step in results linking to the step in the test editor.
  • Added iframe support within popup windows.

April 19th, 2016

  • Added the ability to schedule entire suites of tests.
  • Added test status summaries to each suite on the dashboard screen.
  • Option to prevent screenshots from being sent with Slack notifications.

April 14th, 2016

  • Added assertions for “Element is visible” and “Element is not visible”.
  • Added an option for controlling our auto-retry features which will automatically (and transparently) retry a test when it fails, if it was previously passing. This option can be found under Settings > Step Timing in each test and is enabled by default.

April 11th, 2016

  • The delay applied at the end of each test (before the screenshot is taken) can now be customized under Settings > Step Timing.
  • You can now make “Set Variable” steps “Private” to hide the value.
  • The test listing under each suite now has a column showing the schedule of each test.

April 7th, 2016

  • Launched refreshed designs for the application and Chrome recorder. While almost all functionality is in the same place, a number of improvements and additions have been made to make the application and recorder more intuitive. The start URL is now available for editing at the top of the test editor screen.

April 4th, 2016

  • Firefox has been upgraded from 41.0 to 45.0.1. PhantomJS has been upgraded from 2.0 to 2.1.1.

March 10th, 2016

  • Suite level test defaults are now available. There is a new “Default Settings” tab on the suite settings screen which allows you to set default values for a number of test options such as start URL, browser enginer, screen size and more. These settings will be used by your tests when the tests’ settings are empty or set to “Use Suite Settings”. This allows users to easily apply suite-wide changes in one place.

January 21st, 2016

  • Selenium import has been added. We currently support Selenium v1 .html files. This is the same format that Ghost Inspector exports. This format can be generated using tools like Selenium IDE and Selenium Builder. The import option is available in the “Actions” menu on the suite screen.

January 19th, 2016

  • XPath is now supported (in addition to CSS) for targeting elements in test steps (when prefixed with xpath=).
  • Sizzle is now used as Ghost Inspector’s selector engine, allowing selectors such as a:contains(“Link Text”).

January 14th, 2016

  • Whitespace is no longer trimmed from the front and back of values in the test editor.

January 6th, 2016

  • Ghost Inspector now supports drag and drop. There is a new “Drag and drop” action available in the test editor. The Chrome recorder will also do its best detect and capture drag and drop events.

December 9th, 2015

  • Ghost Inspector App now spans the full browser width, better visual layout for larger screen devices.

December 4th, 2015

  • Test screen size can now be overridden when executing suites and tests through our API
  • A “Screenshot Exclusions” field has been added to test screenshot settings which allows you to specify CSS for elements which should be hidden before the final screenshot is taken. This allows you to hide dynamic elements for more effective screenshot change detection.

November 19th, 2015

  • A number of new screen resolutions have been made available for browser tests under Settings > Screenshots

November 6th, 2015

  • Firefox has been upgraded to v41.0.2

October 29th, 2015

  • PagerDuty can now be triggered when screenshots fail (in addition to test steps)
  • You can now accept a new screenshot as the baseline via a button in our email notifications

October 28th, 2015

  • Step notes are now included in Selenium export files
  • You can now download an entire suite of tests in Selenium format (as a .zip file)
  • A new API endpoint has been added for downloading a test in Selenium format
  • A new API endpoint has been added for downloading a suite of tests in Selenium format (as a .zip file)

October 27th, 2015

  • You can now extract objects from JavaScript into test variables. Objects are stored in their JSON form and can be used in subsequent JavaScript steps.

October 26th, 2015

  • You can now schedule tests to run on a 5 minute interval (in addition to our previous interval options).

August 20th, 2015

  • You can now easily override start URLs when triggering tests or suites using the "Execute with Custom Settings…" option accessible in the dropdown next the "Execute" button

August 18th, 2015

  • We’ve adjust our maximum screenshot comparison area to 1,920 x 20,000 pixels. Content outside of those dimensions will be ignored during the comparison

July 23rd, 2015

  • Added support for interacting with popup windows during browser tests
  • Added "Tab" key option for "Keypress" action

July 14th, 2015

  • Launched integration with HipChat communication platform
  • Added notification option to be alerted only when a test fails (and not when it passes again)

July 13th, 2015

  • Ability to override "User Agent" string when executing tests and suites from the API
  • Variables placed in the startUrl and userAgent fields will be replace with variables passed in when executing tests and suites from the API

July 9th, 2015

  • Launched AWS CodePipeline integration for executing Ghost Inspector tests within your deployment pipelines

July 6th, 2015

July 2nd, 2015

  • Recorder improvements for dealing with non-standard HTML tags in website markup

June 18th, 2015

  • Allow 0% screenshot tolerance setting for detection of extremely small changes

June 11th, 2015

  • Steps show current passing/failing status in test editor

May 28th, 2015

  • Step comments are now shown in test result displays and emails

May 27th, 2015

  • Added transparent auto-retrying for tests that fail when they passed on the previous test run (to combat false positives)
  • Added ability to sort the test listing when viewing a suite

May 14th, 2015

  • Added ability to assign empty values to inputs (clearing out the current value)
  • Improved display of multi-line values in test steps

May 11th, 2015

  • Added ability to adjust (or disable) automatic AJAX waiting

May 8th, 2015

  • Added "Select All" checkbox on test listing screen
  • Removed "Start URL" label from test and added "Start URL" label to result

May 6th, 2015

  • Enabled network filter functionality by default below test steps in the editor
  • Increased file upload limit (for test steps) to 10MB and improved validation
  • Removed suite limitation when selecting tests to run within other tests

May 5th, 2015

April 27th, 2015

  • Launched integration with Slack communication platform
  • Released v2.3.0 of our Chrome recording extension with support for traditional frames and the option to enable recording of URL query strings in selectors
  • Converted Screenshot comparison tolerance setting to a slider with 1% increments

April 20th, 2015

  • Large improvement and expansion of variable functionality:
  • Addition of "Set Variable" command for setting variables directly
  • Addition of "Extract from JavaScript" command for returning values from custom client-side JavaScript and storing them in variables
  • Improvements to Selenium HTML export

April 8th, 2015

  • Custom invoice download in PDF format with the ability to customize business details
  • Released v2.2.3 of our Chrome recording extension with the option to disable screenshot comparison and recording improvements

March 31st, 2015

  • Released v2.2.0 of our Chrome recording extension with a setting panel containing various options

March 17th, 2015

  • Released v2.1.0 of our Chrome recording extension with the ability to record within <iframe> elements
  • Improved rendering of Chinese characters within screenshots

March 12th, 2015

  • Revamp of our online test step editor:
  • Cleaner, more organized designed with quick access to additional options
  • Support for re-ordering steps via drag-n-drop
  • Ability to add informational notes to each test step

March 11th, 2015

  • Released v2.0.0 of our Chrome recording extension with various enhancements:
  • Ability to switch between operation and assertion modes while recording
  • Ability to assert the values of <input> and <select> elements
  • Improved design scheme

March 5th, 2015

  • Added StatusPage.io widget for displaying alerts when there are service problems
  • Test runners now check <select> elements to make sure <option> value is present before assigning
  • Moved test schedule settings into its own section for clarity

March 3rd, 2015

  • Launched PagerDuty integration
  • Notification settings overhaul with ability to set notifications at the account/organization, suite, and test levels
  • Added "Element is not present" assertion type
  • Added ability to duplicate an entire suite
  • Added ability to move tests from one suite to another in bulk
  • Added ability to regenerate API keys from the account screen
  • Changelog added to website