BVA is about defining test cases with data in the middle of Equivalence Classes.

BVA is about defining test cases with data exactly on the boundary between two Equivalence Classes.

BVA can be done independently from Equivalence Class Partitioning (ECP).

BVA is a follow-up step to Equivalence Class Partitioning (ECP).

When defining ECs only program inputs are relevant.

There exists one unique set of ECs for each program.

Every element of an EC has the same behavior with regards to a certain operation.

The values of two ECs may overlap.

• EC1: Customer-ID is a non-empty, well-formed string of the form ‘LNNLL’ as specified;
• EC2: Customer-ID is empty or not well-formed;
• EC3: Birth-Year is an integer in range [1900, 2100];
• EC4: Birth-Year is empty or not an integer or not in range [1900, 2100];
• EC5: Business-Area is ‘SE’;
• EC6: Business-Area is ‘NE’;
• EC7: Business-Area is empty or not in {SE, NE};

• EC1: Customer-ID is a non-empty, well-formed string of the form ‘LNNLL’ as specified; 
• EC2: Customer-ID is empty or not well-formed; 
• EC3: Birth-Year is an integer in range [1900, 2100]; 
• EC4: Birth-Year is empty or not an integer or not in range [1900, 2100]; 
• EC5: Business-Area is ‘SE’;
• EC6: Business-Area is ‘NE’;
• EC7: Business-Area is a non-empty string;
• EC8: Business-Area is empty or not in {SE, NE};

• EC1: Customer-ID is a non-empty, well-formed string of the form ‘LNNLL’ as specified; 
• EC2: Customer-ID is empty or not well-formed; 
• EC3: Birth-Year is an integer in range [1900, 2100]; 
• EC4: Birth-Year is empty or not an integer or not in range [1900, 2100]; 
• EC5: Business-Area is a non-empty, well-formed string of the form ‘LL’ as specified;
• EC6: Business-Area is empty or not in {SE, NE};

• EC1: Customer-ID is a non-empty, well-formed string of the form ‘LNNLL’ as specified; 
• EC2: Birth-Year is an integer in range [1900, 2100]; 
• EC3: Business-Area is ‘SE’;
• EC4: Business-Area is ‘NE’;

If EC=(0, 1) defined on the set of real numbers, then the following values should be tested:

• 0
• 1
• -0.0001 (or some other real value just below 0)
• 1.0001 (or some other real value just above 1)

If the EC is the set of arrays of length 3 containing positive integers, then the following values should be tested:

• [1, 1, 1]
• [maxint, maxint, maxint]

If EC=[0, 1] defined on the set of real numbers, then the following values should be tested:

• 0
• 1
• -0.0001 (or some other real value just below 0)
• 1.0001 (or some other real value just above 1)

If for an input field that accepts only integers the valid EC is defined as the set of values 1 to 9, the following values should be tested:

• 1
• 9

The decision whether a test case has passed or failed.

The test data used to test an application.

The result of the test.

A mechanism used for determining whether a test has passed or failed

Inability to perform the program’s required functions (correctly) 

Wrong/missing statement in the software (code)

A correct program state.

According to an IEEE standard: Mistake made by human (e.g., programmer)

Scenario: Eat 7 out of 12

Given there are 12 cucumbers

When I eat 7 cucumbers

Then I should have 5 cucumbers

Scenario: Eat 5 out of 20

Given there are 20 cucumbers

When I eat 5 cucumbers

Then I should have 15 cucumbers

Scenario: Eat 5 out of 12

Given there are 12 cucumbers

When I eat 5 cucumbers

Then I should have 7 cucumbers

Scenario: Eat 5 out of 12

   Given there are 12 cucumbers

   When I eat 5 cucumbers

   Then I should have 7 cucumbers

Scenario: Eat 5 out of 20

   Given there are 20 cucumbers

   When I eat 5 cucumbers

   Then I should have 15 cucumbers

Scenario: Eat 5 out of 12

Given there are 12 cucumbers

When I eat 5 cucumbers

Then I should have 7 cucumbers

Scenario: Eat 12 out of 20

Given there are 20 cucumbers

When I eat 12 cucumbers

Then I should have 8 cucumbers

TAG visualizes which of the methods that were reused from a previous release have been tested.

TAG visualizes which of the methods that were changed or added since a specified date (baseline) have been tested and tests have failed.

TAG visualizes which of the methods that were changed or added since a specified date (baseline) have been tested and tests have passed (indicated by green color).

TAG visualizes which of the methods that were changed or added since a specified date (baseline) have been tested.

The purpose of ‘When’ steps is to put the system under test in a known state before the user starts interacting with the system.

The purpose of ‘Given’ steps is to describe the key action the user performs with the system.

The purpose of ‘Then’ steps is to put the system under test in a known state before the user starts interacting with the system.

The purpose of ‘Given’ steps is to put the system under test in a known state before the user starts interacting with the system.

The following should be monitored: duration of testing, lines of code covered, functions covered.

The following should be monitored: duration of testing, risks addressed, tests executed.

The following should be monitored: tests executed, test results achieved, risks addressed.

The following should be monitored: duration of testing, risks addressed, functions covered.