Systems | Development | Analytics | API | Testing

No user likes to spend time waiting for a web page to load. No web developer likes a website or app to fail either. It’s important to focus on creating quick loading pages with error-free code. JavaScript is used to build the majority of the dynamic, real-time applications. JavaScript’s strength is in the context of apps that update content dynamically with minimal latency. JavaScript performance testing should be a priority for ensuring a good end user experience and optimal performance.

Welcome to the “A beginners guide to test automation with Javascript(Nightwatch.js)” blog series part 2! If you have missed out on the first part, you can read it here. In this article we will look into the following and as always – feel free to skip to any part you are the most interested in: Code used in this article can be found in Loadero’s public GitHub examples repository here.

In recent years, there’s been a shift towards broader adoption of JavaScript test automation frameworks. Today our customers are using Cypress, TestCafe, Puppeteer, and most recently, Playwright. Plus, they are often using these alongside existing Selenium and mobile test automation frameworks. The options for testing have increased, and depending on your unique testing needs, you may be adopting one or many solutions in your organization.

Some devs use JavaScript in the browser; some use JavaScript on the server. What if you do both?

Welcome to the “A beginners guide to test automation with Javascript(Nightwatch.js)”! This is a three-part blog series to kick start writing web UI automation using Nightwatch.js. In the following parts you will learn: Sounds exciting? Let’s get started! Writing a script in JavaScript (JS) and Nightwatch.js, aka Nightwatch (NW), is simple once you get started and this guide will help anyone regardless of their skill level.

There’s no doubt which programming language is winning the battle for global supremacy right now. JavaScript has powered past the 12 million developers mark, and 5 million of its loyal fans (some 40%) have come aboard within the last three years. Initially thought of as merely a Java spin-out, it is now used to power everything from machine learning libraries to space exploration robots. But to truly maximize the potential of JavaScript, developers have to implement an effective testing regime.

Let’s talk about SPAs. It all starts from a blank page which is subsequently filled with HTML and JavaScript. If we take PHP pages as an example, they already come bundled with the server, which is an advantage in terms of performance, right? For situations like these, server-side rendering frameworks (such as Next.js) come to the rescue. They process the code on the server-side to pre-fill the HTML result page with something (if not the whole page) before it reaches the browser.

As developers, we’ve traditionally rooted out errors in our programs (we’ll call them bugs from now on if that’s ok) by using meaningful log statements. JavaScript has the famous console.log() method for that. But while log statements are good, they are less efficient than a tool that enables you to carry out step-by-step debugging. So in this article, we will learn how to use Google Chrome developer tools (also known as DevTools) to debug any JavaScript application effortlessly.

The year 2015 was marked by a new paradigm shift in web development. Google introduced Progressive Web Applications and JavaScript libraries and frameworks, such as React.js, Angular.js or Vue.js, created new development methodologies. By 2020, the web environment is flooded with PWAs based on reactive programming and built with cutting-edge frameworks.