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.

Consider the following: You go to the Apple Store to pick up the latest iPhone. You get home and turn it on, only to find that the screen is defective, the buttons aren’t working, and every one of the built-in apps is glitching. Thanks to QA tools, this is an extremely unlikely scenario. Before the iPhone reaches your hands, both its hardware and software have been tested repeatedly by a Quality Assurance (QA) team.

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.

Usability is critical for the success of any website or app. To make sure your web-based project is bug-free, you need to run UI tests, many of which can—and should—be automated. Doing so lets you detect issues like bugs, slow loading times, or poor responsiveness so you can fix them before they make a bad impression on users. But while you can find a lot of UI testing tools online, this abundance of options makes it challenging to choose the right UI tool for your project.

Automated testing entails much more than simply creating tests and enabling them. A “set it and forget it” approach won’t get you very far with automated tests — particularly automated browser tests, which interact with the ever changing frontend of your application or website. The true workload ultimately comes with the maintenance and evolution of your tests, so it’s extremely important to design your tests in a logical and maintainable way.

I love this quote, though I’m not quite sure if “Jan Houtema” is a real person. It may be a Paul Graham pseudonym… But in any case, yes, change breaks brittle things and one of the challenges of automated browser testing is to mitigate that effect as much as possible while you design tests for an ever-changing application.

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.