We know that a very simple product or system can generate a vast number of potential test cases. With more complex systems, this number becomes astronomical. This is the result of a factorial calculation! One technique we use to get around this problem originates with designed experiments. Many designed experiments are based on orthogonal […]
We have discussed compliance testing earlier. This is known as testing to requirement. These requirements can be taken directly from a customer specification (when we have one) or derived internally from a requirements review or even both. Compliance testing is the primary method we use to ensure that we are meeting all specifications and […]
To perform embedded software testing, we recommend five phases of testing. These phases may take place concurrently and are as follows: Compliance testing Combinatorial testing Stochastic (or exploratory) testing Extreme testing Attack mode Each of these methods provides some view of the product the other method does not. Of course, testing the product is not […]
We do not need to suffer the pains of the risk due to spot checking. We have a number of alternatives. For example: Modeling and simulation Iterative testing throughout the development Launch AND continue test and verification Launch and continue test and verification reduce volume of customers Relying upon modeling and other forms of simulation […]
We should guard against our organization becoming enamored of the idea of “spot checking”. Spot checking, if done at all, should be based upon facts, calculations and historical record and not due to the logistical inconvenience of a hard date. Spot checking is when we perform a cursory review of the product. Some folks call […]
We have briefly discussed why verification is important to the product quality. Verification does not just address the product quality. Our project work requires verification as well. When we take on a project, we should have the scope articulated in a way that we can confirm that the project did indeed fulfill the objective. As […]
Requirements management and configuration management are required for anything that even closely resembles effective testing. Experience suggests failing in these two areas unnecessarily complicates the product verification activities, and we will show some of those traumas in the next few posts. An iterative and incremental product development process calls for reviews throughout the development process. […]
By: Rick Edwards A good carpenter never blames his tools. There is also an aphorism “it is the poor musician who blames his instrument”. Why do so many good project managers blame their scheduling tool when their project schedule doesn’t fit their desired schedule? Project managers often struggle with documenting task dependencies utilizing the technology […]
I know this is way off topic; however I thought we should post this. Below is a letter my brother and I sent to the Veterans Administration. Our father was in the Special Forces and served multiple tours in Vietnam. The US has been in wars for decades now, and we do not know the […]
We have our requirements, our iterative packages and content defined, and now the developers are producing the iterations. During this time, the verification and test folks have been creating the test cases or details on how we intend to confirm the product performance. Our requirements provide the fodder for our testing. For each requirement there […]