Tag: QA Optimization
7 Signs that You should Consider Investing More in TestingQA 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,...
How to Manage Traceability in Exploratory TestingQA 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...
Think like a Leader, Become a LeaderQA Optimization
Jack from Qualitest UK discusses the amazing time and the thought-provoking lessons he learned at EuroStar in this week's blog.
6 Reasons that Developers fail as Software TestersQA 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...
Communication: The Ultimate Software Testing ToolQA 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...
Considering Test Estimation and NegotiationQA 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.
Extending the Test Basis – Let’s look at the usersQA 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.
Requirements vs. DesignQA 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.
The Top 5 Skills for Future Software TestersQA 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...
Most Commonly Misused Testing Tools and their Appropriate CounterpartsQA Optimization
Tech is full of innovators. The IT industry spends a huge amount of time and effort determining the most efficient way to accomplish various tasks....
Elements of Software TestingQA Optimization
Software testing is constantly evolving and growing as new technologies and methodologies wax or wane in popularity. Different testing professionals may have different definitions of...
Requirements: Into the Mind of the AuthorQA Optimization
It seems well-accepted that it is cheaper to find defects earlier in the software development lifecycle than during dynamic testing or in live operation. I don’t need to include a graph of the cost escalation curve here; we’ve all seen it before. This rule can be applied to all walks of life – putting up a garden shed, building a house, buying a car, running a marathon – you name it and the adage “find problems early to save pain and aggravation later” always applies.