Blog
There’s a lot more to software testing than you may think. QualityLogic’s 30+ years of software testing experience is here to guide and educate you on the finer points of software testing and the business considerations you may come across.
Software Quality Assurance (SQA) — a planned and systematic approach to the evaluation of the quality of and adherence to software product standards, processes, and procedures.
Agile development is the concept of churning out a continuous stream of product releases, most of which are expected …
Is quality assurance important to your product? How about to your brand? If the answer is yes—and I hope it is—then perhaps it’s time to think about offering your QAs the spotlight at the retrospective table.
What’s the definition of a retrospective? A retrospective is …
If automated testing is the backbone of agile testing, then exploratory testing is the heart. Like any ‘good heart’, agile exploratory testing seeks to understand the ‘why’ and ‘how’ of a user experience (UX) through empathy. To be successful, both developers and testers must explore …
If you haven’t heard of design thinking yet, odds are you will soon. Where business is concerned, design thinking is no longer something done just by the creatives of an organization. And, it does not simply mean ‘build pixel perfect wireframes’. Design thinking is a …
Let’s talk about the benefits of exploratory testing vs scripted testing, and the ‘ad hoc’ debate. In the context of software testing it’s interesting to parse the 16th century Latin roots of this modern idiom. Today, the phrase ad hoc is often synonymous with sloppy …
The name says it all: “Big Data.” The automation of a myriad of information handling services, especially in the last decade, has facilitated the collection of truly massive amounts of data. This information contains hugely valuable information but, by its very volume, it requires new …
2017 was the year bugs ate our computers. While we pondered the implications of machine learning, multiple software bug incidents reminded us that software programs are only as good as the people who code them. And, computers only do the things we define for them. …
The power and fatal weakness of software is its ultimate malleability. It can be quickly and easily changed by drastic degrees. This one inescapable aspect would be good cause to abandon software entirely if it weren’t for its extreme power to make our machines do …
Where unit tests are deeply involved in the functionality of individual code modules, the integration test process is focused on the system as a whole and the complete combination of those modules. It is deeply concerned with how they communicate with each other. As its …
Risk-based testing (RBT) is exactly what it sounds like, testing your software based on risk. We know from last week’s blog that circular definitions like this annoy me, so let’s break RBT down to some measurable components.
The first and most obvious question is: what …
Businesses, especially software-centric businesses, have dramatically increased the velocity of their operations. Software development itself has gone from bi-annual version updates to weekly releases via the Agile methodology. Managing this eye-watering rate of change has brought every business function to the necessity of monitoring Key …
Often, requirements-based software testing is defined something like this: “a testing approach in which test cases, conditions and data are derived from requirements.” This sort of circular explanation is annoying — and unhelpful.
What are Software Requirements?
Google defines requirements as “a thing that is …
