BCM – Basic Configuration Matrix Rikard Edgren
The variety of configurations (operating system, browser, language etc.) can look overwhelming; and it is impossible to test all possible configurations for Servers and Clients. On the other hand there are certain platforms that are more probable to uncover defects.
This is just common sense, but I haven’t seen any terminology for handling this in an effecient manner, so let’s call it BCM.
Basic Configuration Matrix is a short list of platform configurations that will spot most of the platform bugs that could exist in your currently supported configuration matrix.
The simplest example is to use one configuration with the oldest supported operating system, oldest browser etc; and one configuration with the newest of all related software. A more advanced example could use several configurations that use different languages, Application Servers, authentication methods et.al.
If it would take too long to run most tests on BCM; alternate between the configurations while testing your product. Do variations on configurations when appropriate.
The BCM is extremely handy tool when communicating coverage. When talking to persons who know little of testing, they understand that doing this selectiong of configurations is very effective.
Another way to do this is to test as many combinations as feasible with automatic (regression) tests,
and do deeper testing with best representatives configurations.
Can u please share the template for the BCM ?
Hi Srinivas
There is no template.
BCM is a concept.
But it is used at many places, and probably is just a table with rows and columns.
When I used it most extensively we included things like OS, system language, Office version, browser, graphics card, screen resolution, color scheme (it was a graphic intense software with accessibility requirements)
You should first learn about which things are important to test, you can’t cover everything anyway.
[…] Basic Configuration Matrix is a short list of platform configurations that will spot most of the platform bugs that could exist in your currently supported configuration matrix. The simplest example is to use one configuration with the oldest supported operating system, oldest browser etc; and one configuration with the newest of all related software. A more advanced example could use several configurations that use different languages, Application Servers, authentication methods et.al. Often it will take quite some time to run most tests on BCM; so alternate between the configurations while testing your product. Do variations on configurations when appropriate. […]
[…] 5) Where? a) The environments where the software will operate and interact. Specific hardware and software? b) Which environments can you afford to use; how far can you get with Basic Configuration Matrix (http://thetesteye.com/blog/2008/05/bcm-basic-configuration-matrix/) […]