Systems | Development | Analytics | API | Testing

According to a study by Stack Overflow, developers spend approximately 50% of their time debugging and fixing issues in their code. As a software engineer, I understand the problem first-hand. We pour our heart and soul into building applications, yet bugs persist despite our best efforts. While some are caught during compilation, others lurk undetected, potentially causing damage and financial woes. That’s why rigorous testing of applications becomes crucial before market launch.

I live in Copenhagen. The winter is dark and cold, and I need a coffee to get my day started. Luckily for me, there is a cafe in the building. I find enough energy to get myself into some decent winter clothing and leave the comfort of my warm apartment. The patient staff at the cafe gets me my Cappuccino and gently asks “Would you like to pay with the App or a Card”? I said, “with card please” – as do 90% of people in the Nordics.

In the ever-changing realm of software development, the concept of mock objects often emerges as a source of optimism amidst the tumultuous testing and debugging process. These simulated objects are not just mere jargon in a developer’s vocabulary; they are vital instruments that imitate the behavior of actual objects in controlled settings.

The role of the software tester has expanded well beyond the traditional task of finding bugs. Today’s testers are pivotal in fostering high-quality, robust, and user-focused products. This comprehensive article explores the multi-faceted role of testers, emphasizing the shift towards a proactive quality mindset, technical and analytical skills, strategic involvement, and continuous learning in the pursuit of excellence.

There are many techniques for software testing. However, if you haven’t heard of or used fuzzing, also known as “fuzz testing”, this may be the best post you have ever read. This article will explain what fuzzing is, from its inception in the late 1980s to its evolution to be “smart” today. After that, this article will explain how to use smart fuzzers like Jazzer and Jazzer.js to fuzz Java and JavaScript code, respectively.

Have you ever found yourself struggling to identify relevant selectors while writing automation test steps? Have you considered an alternative approach to crafting readable test scenarios without relying on tools like Cucumber, ensuring accessibility to both technical and non-technical stakeholders? If you’ve pondered these questions, this blog post is tailor-made for you.

In the ever-evolving landscape of software testing, the advent of Artificial Intelligence (AI) has not just been a game-changer; it’s been a paradigm shift. Test automation, once a static process, has metamorphosed into a dynamic and intelligent entity, reshaping how we approach quality assurance.

Selenium WebDriver has emerged as a potent tool for web automation, allowing testers and developers to simulate user interactions with web applications. However, the web environment isn’t always straightforward. Modern web applications often open multiple browser windows or tabs, presenting a challenge when automating tests. Understanding how to handle these multiple windows within Selenium WebDriver is crucial for effective automation.

In software development, an API-first approach has emerged as a powerful methodology for building robust and interoperable systems. An API, or Application Programming Interface, acts as a set of rules and protocols that enables different software applications to communicate with each other. It defines how different software components should interact and exchange data.

Postman is one of the most sought-after tools when it comes to API testing. Whether you’re new or experienced, this tutorial simplifies API testing using Postman. We’ll cover the basics, explore testing techniques, and showcase implementable skills in this blog. This blog is derived from Pricilla Bilavendran’s workshop on Postman with The Test Tribe.