Let’s agreed at the beginning on the test conditions/scenarios is what we need to test and the test cases/procedures is how we’ll test and prove that.

At first, let’s go through a test analysis strategy inherited from the Risk-Based Testing.

First of all, the software requirements are the mentor of the affinity diagrams.

It’s the layers strategy; classify your test item into the following four layers:

-          Business layer.

-          Application layer.

-          Database layer.

-          Integration layer.

Each layer has its own attributes which in mix with the affinity diagrams will be create the test diagrams for your test items.

The business layer briefly, talks about the business processes need to be implemented and tested.

The application layer briefly, considers the GUI and data validation scenarios which cover the application movements and data correctness

The database layer briefly, covers the data manipulation scenarios and the data itself affection

The integration layer briefly, focus in two areas internal and external integration

Each layer has the three common paths, primary, alternative and expectations.

Now let’s take an example for save as MS-Word.

The BL here, save a copy from a document in same folder with different name or same name in different folder.

The AL here, using a shortcut key, use the command from menu, use a function key.

The DBL here, using special characters, or using special name conditions

 The IL here, about import file and save it, save into network path, etc...

Now can you create a test procedure for the mentioned test scenarios or cases?

Regards,

Samer Desouky

Test Leader, MCS

ISTQB  CTAL-TM

www.mcsoil.com

a.samer@mcsoil.com

21, Nov 2010 12:59 PM