The purpose of exploratory testing is to learn how a particular area of your testing is working while using your skills as a tester to offer insightful input to your team. Through exploratory testing, you can ensure that all bugs are detected, and developers can fix them in time for the product release.
“The way I do work is to lead by a good example, and that’s why I’m trying to set up Xray as an example for test management and reporting.” Sharon Lundgren, Manager IT Quality at IU About the Company IU (International University) is the largest university in Germany. One of Europe's most cutting-edge educational institutions, IU has over 10,000 practice partners, over 1,000 lecturers, and about 480 professors.
“Did you know that there are 100+ different types of product risks that can affect your software?” Dan Ashby | Head of Quality Engineering at PhotoBox Exploratory testing must be a part of your testing strategy due to the testing effectiveness of your current tests, the ability to find differences in the code, and the ability to remove roadblocks where defects tend to hide.
Playwright is one of the most used frameworks for end-to-end testing of web applications; it supports all modern browsers and has broad community support. If you are considering testing your web applications, this is a tool to consider. Whatever your test execution strategy may be, do not forget to consider visibility and the integration capabilities of the tools you wish to add to your tool belt.
More people use mobile devices to access websites and applications than laptops and desktop computers. According to Statista, mobile traffic share is over 54%, surpassing desktop computers as the most used device to access the internet in 2022. Mobile also fuels 45% more financial decisions, according to the State of Mobile 2021 report. If your app isn’t optimized for mobile, it may be undervalued and underperforming financially.
Software testability measures how simple it is to test both the system as a whole and each individual component. Testability might mean different things for different members of the software development lifecycle. Remember how deeply frustrating it was to rewrite dozens of UI tests when a front-end developer made a small change that broke all the locators? Or the several restless nights spent fixing minor performance issues that aren't reproducible on the local machine?
Does your organization use testing as a catch-all safety net for quality? Testers can often become the gatekeepers and decision-makers regarding whether something is ready to be “signed off,” which creates silos and can slow down releases. Nowadays, there is a lot more talk and emphasis in the testing and QA industry about shifting towards a quality engineering approach to build quality-in, and for everyone to contribute to the overall quality of what is being delivered.
Every organization knows what quality should look like for the products they work on. However, what’s the best way of knowing whether the obtained quality compares to the expected quality of the product(s)? Quality can be both quantitative and qualitative. Many questions could be asked to determine quality. For example, "How do you feel about the product you use? How easy is it to use? Does it behave as expected? Do customers keep coming back to use our product?
