Systems | Development | Analytics | API | Testing

Welcome to our guide on how to perform browser testing with Ghost Inspector! If you’re reading this, you may be trying Ghost Inspector for the first time or considering it as a tool to help you streamline your company’s testing efforts. Our goal is to provide you with a simple way to catch bugs on your website or web app before they cost you. In this post, we’ll go over the basics and guide you through how to get started with Ghost Inspector for browser testing.

Introducing Zac ODonnell, the Manager of Software Engineering at EnergyCAP, who shares his testimonial on how Ghost Inspector has revolutionized their development process. EnergyCAP helps businesses effectively manage energy usage, utility bills, and carbon footprint while achieving substantial savings. However, they faced challenges in keeping their product running smoothly amid frequent changes and security patches.

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.