Because retesting and regression testing have many similarities, it’s easy to get them mixed up. Both are software testing methods used to maintain the usability of a website or web app, and both involve testing your software repeatedly. Thankfully, there are some key differences between the two that are easy to remember when learning how to distinguish one from the other. Read on for a simple breakdown of retesting vs regression testing, so you never end up confusing them again.

Selenium IDE is a popular open-source tool for recording and running automated browser tests. You can use it to interact with a browser the way a human would, doing things like navigating to URLs, filling in forms, and clicking on links and buttons. You can also use “assertions” to verify things are working as expected, like checking that elements are present, text is present, inputs contain certain values, et cetera.

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.