This year has been nothing if not exciting in the software testing and development space.
Now, as we look back in at the year in review, we also wanted to take a look at what our readers found to be the most interesting, valuable, and informative as they navigated 2018.
Here’s what we found were the top 10 blogs of the year:
- 8 Essential Tips for Building a Cross-Compatible Website – Understanding the importance of a web application that works across browsers is one thing, but developing for it is another. While you shoudn’t strive to have your design look exactly the same on every browser, there are a few ways to make sure that you’re providing a consistent user experience.
- Selenium vs Cypress: Is WebDriver on Its Way Out? – There’s a new kid on the block for open source test automation tools, and everyone’s talking about how Cypress may be an alternative to Selenium. But while some have posed that Cypress signals the end of an era, we’re not so sure that Selenium is going anywhere anytime soon.
- A Brief History of Web Browsers and How They Work – We all know the basic functionality of the browser — it’s what connects you with everything on the web. But why do different browsers respond differently to websites, and why is there more than one to begin with? We answer all your burning questions with a short history lesson.
- 5 Lessons Agile Teams Can Learn From Netflix – Similar to Agile development, it seems like Netflix also strives to focus on fast feedback, iterative changes, and cross-collaboration. By taking a closer look at the way the company operates behind the scenes (or should we say, behind the screens), Agile development teams can learn quite a bit from Netflix.
- Record and Replay Testing vs. Scripting: Which is Right for You? – With so many tools on the market claiming to help you automate your tests, what do you choose? Between Selenium and record and replay testing, it can get a little confusing. All test automation tools have certain strengths; once you know how to leverage them, the answer should be more clear.
- The Div That Looks Different in Every Browser – A guy named Martijn Cuppens coded a div which made a fairly simple green square. However, when you look at it across different browsers, it transforms completely into another shape. His example provided a fun insight into how CSS can go wrong and why it’s important to test across browsers.
- How to Fix a Flaky Selenium Suite – One of the most common headaches for testers when it comes to Selenium is recurring flaky tests. In order to put an end to the flakiness, we have a few tips to keep your builds stable.
- How to Increase Test Coverage Over Time With Automation – When it comes to software quality, we want to test as much code as humanly (or mechanically) possible, right? Actually, yes and no. For each test cycle, it’s important to consider multiple strategies for measuring test coverage and put a system into place where it can be maximized over the long-term.
- 6 Questions to Ask Yourself Before You Decide What Test Cases to Automate – Before you jump into test automation head first, you should evaluate how it is actually fitting into your organization. By asking these questions, you can get a better idea as to whether automation is the right move, or if you should take another route.
BONUS: Many of the tutorials and resources from our Selenium 101 series also popped up in visitors’ most viewed. Check out our Selenium 101 toolkit to learn everything from how to test your login process to running your tests in two browsers at the same time.
Thanks for coming along for the ride. We’re excited to see what the New Year brings! See you back in 2019.