Tag: QA Optimization

Future of Medical Device Testing
Blog

Qualitest’s Neri Lavi Joins Healthcare Weekly Magazine’s Podcast to Discuss the Role of AI in the Future of Medical Device Testing

Healthcare Medical Devices QA Optimization

read more

Blog

New Testing Show Podcast: Test Coverage – An Expert Evaluation

QA Optimization

Elle Gee along with Perze Ababa, Matthew Husser and show producer Michael Larsen sharing expert insights on some of the salient factors related to test coverage.

read more

White Paper

Analyzing Requirements

QA Optimization

In this article, I have attempted to bring together ideas on inspecting and analyzing requirements based on reading techniques as procedural approaches encompassing common checklist methods to achieve better defect detection rates as early as possible in the development lifecycle.

read more

Blog

7 Signs that You should Consider Investing More in Testing

QA Optimization

A frequent question that is raised in the software technology world is “How do I know if I have tested enough?” In this technological era,...

read more

Blog

How to Manage Traceability in Exploratory Testing

QA Optimization

Exploratory Testing is software testing approach that simultaneously incorporates learning, test design and test execution. While the software is being tested, the tester generates new...

read more

Blog

Think like a Leader, Become a Leader

QA Optimization

Jack from Qualitest UK discusses the amazing time and the thought-provoking lessons he learned at EuroStar in this week's blog.

read more

Blog

6 Reasons that Developers fail as Software Testers

QA Optimization

Software testing is more than just a job to some; it’s a lifestyle. However, a question that seems to be asked frequently is, “Why can’t...

read more

Blog

Communication: The Ultimate Software Testing Tool

QA Optimization

A lot of pros in the industry spend a good chunk of time talking about software testing tools; when they do, typically they mean programs...

read more

White Paper

Considering Test Estimation and Negotiation

QA Optimization

Test estimation is a forecast of the projected cost and duration of testing which is agreed upon between the testers and enterprise which requires testing. It is a means for discerning information which will need to be fed back in to the business. It is often said that testing is a Risk Mitigation exercise, but as the testing process itself cannot mitigate risk, it would be a truer statement to describe the testing function as a tool by which the business gleans information enough to mitigate risk. It’s likely that most of those reading this white paper will fall into the bracket of estimating in accordance with what should be done as a set of testing tasks. This is not incorrect; however, to only consider testing estimation against what one believes to be the correct list of testing tasks and depth of testing is an incorrect way of approaching test estimation.

read more

White Paper

Extending the Test Basis – Let’s look at the users

QA Optimization

When we discuss test analysis, we do so in reference to the test basis that collection of documents, standards, and attitudes that we use to guide our testing. Unfortunately, it seems that for some testers the test basis begins and ends with the requirements as captured by a business analyst or a requirements analyst. Many testers seem reluctant to push back on the requirements, to look beyond what is written down. This is understandable, as many project managers are even more reluctant to extend project scope and many developers are wary of what they see as tester-driven development; we are not all used to having our opinions listened to and respected.

read more

White Paper

Requirements vs. Design

QA Optimization

Some people say that requirements are about what you build, and design is about how you build it. This simplistic statement may sound right, but there are two potential problems with condensing the matter in this way. First, it makes it sound like there should be a sharp boundary between requirements and design, when that’s not really the case. In reality, the region between the two is actually very grey and foggy, not a crisp line at all. I prefer to say that requirements should concentrate on what and design should concentrate on how. It is important to explore possible designs that might satisfy certain requirements; a valuable method for assessing the clarity, correctness, completeness, and feasibility of these is through prototyping. Getting customer feedback on prototypes helps ensure you’re on the right track.

read more

Blog

The Top 5 Skills for Future Software Testers

QA Optimization

The software field grows every year, and so do all of the individual facets it contains. We can personally attest that software testing companies are...

read more