Information Technology Reference
In-Depth Information
To test modern-day software systems, you need to master the latest testing tech-
niques and methodologies to combat the systems' large size and complexity and
become successful in testing these systems.
For the test manager, to deal with testing any such huge and complex system is
the old and proven divide-and-rule methodology. Have a mug of beer (if you are a
teetotaler, then maybe you can do the Mountain Dew) and sit down with a paper
and pencil. Do not panic yet (keep it for later)! If you have previous experience with
managing a similar test project (even if it was a smaller monster compared to the
present one) and if you remember the details, then you are almost there. If not, then
you can search your company archives to find out if any similar project was ever exe-
cuted and if any project data is available. If you fail here, then there is still one more
avenue available for your rescue. Your friends! If your friends fail, then you have
the ultimate tool at your disposal: Google and the Internet! Find it there through
searches, forums, and so on. If that fails, then read this topic. So you are there! Now
you can easily manage the show. Have lots of confidence and be positive!
If you also possess domain knowledge (e.g., supply chain management, finance,
telecom) and the project belongs to your domain, then you are in a safe boat. If
domain is not your cup of tea, then do not worry! There is still some hope out there.
You can take help from your same old and trusted friends, Google and the Internet.
You have come to the conclusion that the project is big and complex because you
have heard about it from the delivery and senior managers. But if you remember cor-
rectly, then you must have seen the requirements and design documents. They are the
lifeline for you. Without them, you cannot survive. So take good care of them and go
through them again and again. After you go through them four times, you will see
light at the end of the dark tunnel. You will have a good picture of what is required for
the project. You will also have a good idea of what is to be done and how to do it.
Humor apart, you can win over complexity by the same old divide-and-rule method-
ology. Actually complexity comes either from big size or from the intricacy of things. If
something is intricate, you can enlarge its image and then you can have a big picture with
less intricacy. So you cut pieces from the enlarged image and now you can see simpler
things. If the size is already big, then you can cut pieces to make them manageable.
In the case of software testing projects, complexity plays its role mostly in func-
tional testing. The best approach is that you divide the software application into
modules and then divide the modules into submodules. Once it is done, you can
then understand functionality, workflows, and all other aspects for each of these
components. Once you understand each and every piece, summing them up gives
you the bigger picture.
The following case study is a good example of dealing with complexity.
3.2.1
Case Study on Complexity Management
Once I worked as a domain expert on a test project. There was one module that was
very difficult to test.
