Strategy Archives — Rapid Software Testing

Exploratory Testing 3.0

Mary Alton — Fri, 26 Feb 2021 17:11:13 +0000

In the beginning, there was testing. No one distinguished between exploratory and scripted testing. Jerry Weinberg’s 1961 chapter about testing in his book, Computer Programming Fundamentals, depicted testing as inherently exploratory and expressed caution about formalizing it. He wrote, “It is, of course, difficult to have the machine check how well the program matches the intent of the programmer without giving a great deal of information about that intent. If we had some simple way of presenting that kind of information to the machine for checking, we might just as well have the machine do the coding. Let us not forget that complex logical operations occur through a combination of simple instructions executed by the computer and not by the computer logically deducing or inferring what is desired.”

https://www.satisfice.com/blog/archives/1509

The post Exploratory Testing 3.0 appeared first on Rapid Software Testing.

Heuristic Test Strategy Model

Mary Alton — Fri, 14 May 2021 18:25:41 +0000

The HTSM (v.5.7.5) is a set of guideword heuristics designed to help you think better about test strategy. It includes four focus areas: test techniques, project elements, product elements, and quality criteria categories. You can use it casually or rigorously. ... Learn more

The post Heuristic Test Strategy Model appeared first on Rapid Software Testing.

How to Evolve a Context-Driven Test Plan

Mary Alton — Fri, 14 May 2021 18:30:41 +0000

This is a process guide for creating a good test plan within the RST methodology. It consists of seven tasks. The tasks can be performed in any order, or simultaneously and iteratively.

https://www.satisfice.com/download/building-a-context-driven-test-plan

The post How to Evolve a Context-Driven Test Plan appeared first on Rapid Software Testing.

Rapid Testing Guide to Making Good Bug Reports

Mary Alton — Sun, 16 May 2021 02:38:49 +0000

Bug reporting is central to testing. The bug report, whether oral or written, is the single most visible outcome of testing. And the quality of your reports is probably the single most important factor that determines your credibility as a tester. This document describes bug reporting from the perspective of Rapid Software Testing methodology. Throughout this guide I will distinguish between what is expected of “supporting testers” (anyone helping the test effort temporarily or intermittently but not committed to the testing role or perhaps even that project) and “responsible testers” (those who assume the role of tester on a project and commit themselves to doing that job well over time).

https://www.satisfice.com/download/rapid-testing-guide-to-making-good-bug-reports

The post Rapid Testing Guide to Making Good Bug Reports appeared first on Rapid Software Testing.

Test Cases and Coverage

Mary Alton — Fri, 14 May 2021 18:37:31 +0000

At the beginning of the project, you don’t yet know how to test it. To develop a relevant test strategy, you must learn the product. There may be many ways for you to learn about the product—by attending meetings, talking to people, reviewing project plans, studying designs or sketches. You may even have an opportunity to work with the product directly; with a previous version; with a mockup or prototype; or with a part of the product.

Without a good deal of that learning, you cannot know what test cases should describe or contain—so instead of the typical fine granularity of test cases, consider the broader notion of coverage areas.

https://www.developsense.com/blog/2018/06/test-cases-and-coverage/

The post Test Cases and Coverage appeared first on Rapid Software Testing.