Functional testing feels like the bane of one’s existence when things are running on a deadline. No matter the codebase or structure, there’s just so much to do. It also takes a ton of time if you’re doing it manually, and the inefficiency is an atrocity. As one of the final steps before deployment (usually before the non-functional tests start), we have to test everything relating to the functional requirements of the software.

We all are witnessing the growth and evolution of low-code/no-code platforms. Few might still be confused about what this is all about. Don’t feel intimidated, you are not alone, many people are unfamiliar with these terms. This blog will give a gist of it to understand the current revolution of low-code and no-code platforms/tools. We can see more in detail about the history, features, merits, and demerits and how can you adapt and start using them in your organizations.

Working in software development as a tester, it can be difficult to find time to improve the testing process when you are the bottleneck to release with lots of tickets, stories or features to test. I am currently a QA Lead at Cera Care, one of the fastest growing healthcare startups in Europe. Working in this fast moving environment is very challenging for my team, where features are prioritised over anything else and teams have up to 6 developers to 1 QA engineer.

Kubernetes shouldn’t be reserved for production. Using local Kubernetes in development means you can build and test your service using the same technologies as your live deployments. Some organizations provide a shared Kubernetes cluster for development activities. Others offer on-demand virtual clusters that serve staging environments for significant changes.

Test automation has undergone a steady evolution since its inception. While the process of writing test cases to test the software remains the same, the “how” part keeps changing. Sometimes, we like to perform simple and plain test script development as we did in the 90s using a spreadsheet. Sometimes, we record our test cases and run them through programming languages as we did in the 2010s using Selenium.

When developing web applications, one of the important things is to provide smooth accessibility of your product to the clients. But that is not an easy task to accomplish as several factors come into play. Software testing requires coverage of many different devices, environments, and conditions. We in Loadero provide features to use different browsers, run tests from different locations, set different fake media for webcam and mic simulation, etc.

Some enterprises are vacillating about migrating from on-Premise SAP HCM to cloud-based SAP SuccessFactors. But in the future, they will be forced to switch, as the on-Premise legacy system is not designed to keep up with the pace of the upcoming consumer-driven market. Even SAP’s own announcement about the year 2027 as the deadline for SAP ERP HCM support makes the migration inevitable.