For so many years, the companies have relied on a group of people for quality assurance – Testers, QA Engineers, etc., to be vigilant and help software development teams to deliver high-quality applications. We spent our days testing, reporting defects, debating business requirements, and wondering if it was a feature instead of a bug. Perhaps the world is changing; we understand this new era requires different approaches, breaking the silos and collaborating more.
Hello everyone 👋 Hope you are doing great. As a Tester, you might have received a lot of feedback from different people. Have you ever thought some simple tips can help to sharpen your testing skills? Yes, changing your mindset can bring a lot of changes to your daily routine work, thought process, and career. Have you ever felt that being open to the current bad situation caused less stress and impact on you? Are you reacting to every mishap around you?
The owners and makers of web applications always try to carve up a section to represent their mobile applications in the footer tab like this on Myntra: Or showcase it with lines that show that their app has much more to offer than their website like Uber: And sometimes, dedicate a complete section on the top 25% screen of the website like Makemytrip: Screen space is very valuable in a web application.
A common theme among most software testing organizations is their escalating interest in Test Automation. While test automation has grown in popularity, there are still many myths and biases surrounding it. Such myths can unknowingly create a self-limiting boundary and negatively impact the possibilities of test automation. In this article, I will discuss some common test automation myths and biases that people have towards test automation.
The world is entering a new age of technology. Low-code/no-code tools are already becoming a mainstay for many global teams. By going no-code/low-code, teams can now fill in the gap between the accelerating demands of application delivery and team skill sets. While these tools are nicely on their way to becoming mainstream for development, similar ones for test automation are pushing their way into the market.
The open-source movement has become the most talked-about topic in the tech industry for the past two decades. We see a huge demand, inclination, and adoption of open-source software by organizations as well as software workers. This quest for open source will only grow with time, and as testers, this opens up an array of opportunities for us as well as testing and tech communities. In this article, I have condensed my thoughts on Open Source for Testers.
Organizations worldwide are adopting open-source software to drive technological innovations. Testers look beyond the obvious benefit of cost while embracing open-source test automation tools. The reliability, transparency, flexibility are added benefits of choosing an open-source test automation tool. Saving time is saving money! Open-source tools save time reinventing the wheel to build your test automation framework from scratch.
Even with the increasing adoption of Agile and DevOps, many organizations still consider testers the gatekeepers of quality and are solely held responsible for the quality and approving releases. Such organizations blame testers for a missed production bug. No matter how much you test, a few bugs can still slip through the testing phase & reach production. Every software tester would have come across a situation of a missed bug. For many testers, it’s a terrifying nightmare.
I’m happy to announce our financing of $4.6M led by Accel and STRIVE, with participation from BoldCap and a host of well known entrepreneurs and operators 🎉 These include Shanmugam Krishnasamy, co-founder and CTO of Freshworks; Kiran Darisi, co-founder and VP of engineering at Freshworks; Parsuram Vijayasankar, co-founder and principal engineer at Freshworks; Vetri Vellore, CEO of Ally.io; Nitesh Banta, CEO at B12; Ioann Fainsilber, Co-Founder at Pintek, among others.
