You are here

Testing

Boundary Value Analysis (BVA)

A boundary value is any input or output value on the edge of an equivalence partition.
Boundary value analysis (BVA) is based on testing at the boundaries between partitions.
Here we have both valid boundaries (in the valid partitions) and invalid boundaries (in the invalid partitions).

Multiple Condition Coverage (MCC)

Multiple Condition Coverage is also known as Condition Combination Coverage, or MCC.
MCC coverage takes the structure of a decision into account.
Each decision is made up from conditions, which are combined by logical operators (and, or, not).
Roughly spoken, to get 100% MCC for a decision, all combinations of true and false for the conditions in the decision have to be evaluated.
In Multiple Condition Coverage for each decision all the combinations of conditions should be evaluated.

Modeling GUI structures with GraphWalker

I wrote prior to the release of GraphWalker 3. So keep in mind the not all information in this article is valid for GW3. I'll make an updated version soon.

When modeling for a GUI of a system. It can be hard to find the best way for representing the modeled behavior on the system.

One have to think about haw to model what the tests interacts with. For bigger structures there are several approaches. Here are two approached, which are
frequently applied.

Modeling for GraphWalker 201

I wrote prior to the release of GraphWalker 3. So keep in mind the not all information in this article is valid for GW3. I'll make an updated version soon.

JavaScript Enabled Modeling

I have played a little around with GraphWalker and JavaScript enabled models for ESFM. The “-j” option

[-j]

Enable JavaScript engine

java -jar graphwalker-2.6.3.jar offline -f MBT201.graphml -g RANDOM -s REACHED_VERTEX:End -j > output.txt –x

Output:

Start

Modeling 101 for GraphWalker

I wrote prior to the release of GraphWalker 3. So keep in mind the not all information in this article is valid for GW3. I'll make an updated version soon.

Here under some examples on hos to model different “code” structures.

The following examples are without any Graphwalker related constraints. This is only intended for showing how to model the structures. So no Guards,
weights and javascript enabled in these model exambles.

Model Based Testing with GraphWalker 2

I wrote prior to the release of GraphWalker 3. So keep in mind the not all information in this article is valid for GW3. I'll make an updated version soon.

Model-based testing is a new and evolving technique for generating a suite of test cases from requirements.

Testers using this approach concentrate on a data model and generation infrastructure instead of hand-crafting individual tests.

Model-based testing depends on three key technologies:

DSTB Conference and answering a question in detail. BVA as a model.

Yesterday I spoke at DSTB yearly conference. It was a great day, and I talked to a lot of great testers. Luckily I also got some got feedback on my presentation about Model Based Testing (link Supplied in the bottom of this blog post).

I also received a question about modelling a Boundary Value Analysis (BVA) test as a model. Even though I gave a for filling answer in my session. I found the need to post it here.

Performance Testing Questions. Load, Volume, Soak, Spike And Stress testing

It has been a couple of years since a last designed, implemented and executed a performance test. But a few weeks ago I did receive a couple of questions about. I came with answer from the top of my head. Not all bad I think.
"Can you give me a short explanation of: Load testing, Volume testing, Soak testing, Spike testing and Stress testing"
The short quick answer from me:

What is Use Case Testing

Before explaining Use case Testing lets first understand what is a Use Case

A Use case is a description of a particular use of the system by the end user of the system.
Use cases are a sequence of steps that describe the interactions between the user and the software system.
Each use case describes the interactions the end user has with the software system in order to achieve a specific task.

Decision Table Testing

A decision table is a tool for both testing and requirements development. They are essentially structured with the purpose to formulate requirements when dealing with complex “business” rules/logic.

Pages