We’re excited to introduce a new (and much requested!) feature to the Ghost Inspector community: Explicit Window Targeting. Now you have the power to specifically target which window or tab you want to focus on during your test steps. Usually, when you use a CSS selector in your test, Ghost Inspector’s test runners go through all the available tabs to find the first matching element.
Whether you’re a solo developer or part of a larger team, it can be challenging to keep up with ever-evolving customer requirements and testing standards. In our latest case study, we dive into the world of WordPress plugin developer Justin Labadie who uses Ghost Inspector to automate acceptance testing and ensure his plugins meet customer needs. Learn how Justin was able to dramatically reduce development time, decrease bugs, and improve overall customer satisfaction.
Automation testing has been gaining popularity as a reliable, scalable, and cost-effective alternative to manual testing – and rightfully so. With the right testing tools, QA teams can scale their testing processes quickly. In this article, we’ll talk more about how it works and how to get started with a tool like Ghost Inspector.
Jira is one of the most popular task management products available today, and for good reason: it's been around for a long time. The team at Atlassian is constantly working to improve the way users can utilize their software, but for a long time if you wanted to integrate with Jira as a developer, your options were generally limited to the Jira API.
Here at Ghost Inspector, we’re continually rolling out changes that we think make our customer's lives better. Occasionally that means undoing some bit of logic we created or allowed in the past in order to move the product in a direction that makes it more powerful for everyone. We have a couple of changes coming next month that we think are going to be helpful to our customers, but they do change how some logic currently works.
Keeping up to the pace of software changes with good acceptance tests is challenging, and can often put a lot of pressure on the relationships between teams. Being able to detect issues faster and earlier in the development cycle is crucial to shipping good software quickly, but communicating those changes is always challenging -- and if software changes, so must the tests.
We've recently released a new plugin for Netlify that allows you to automatically run Ghost Inspector tests on every deploy, including deploy previews! By default, Netlify deploys your production branch on every change. To enable deploys for other branches, follow the Netlify instructions: With branch deploys enabled, you can now run Ghost Inspector tests on your website before deploying to production!
Quality assurance is a broad initiative. Ghost Inspector strives to be an all-in-one tool when it comes to browser automation. However, QA teams often use a range of products to cover all their testing needs, like API testing and load testing. This can lead to testing-related data being scattered in various places. QADeputy is a service that aims to centralize your QA operations — and it integrates nicely with Ghost Inspector.
Here at Ghost Inspector, we're continually rolling out new browser versions and automation logic updates. However, this month we've got a number of big changes launching at once and I wanted to discuss each in a little more detail. Here's a rundown of what's being added or changed — and how it might affect your tests.
While continuous integration is a common practice for most development teams, the stateful nature of WordPress makes it difficult, but not impossible, to setup. For our open source WordPress plugin, we wanted to integrate our standard build and test process for every pull request using CircleCI. While it might be easier to setup a permanent staging environment, we wanted every build to be isolated for dependable testing.
