Knowledge Sharing - Testing

This is a preparation for tomorrow SDF class. A recap of the Testing methodology. Just some sharing on Testing.


Work Products of Testing


Test Plan (Composite deliverable)

Define what will be tested.
Consists of
1. Test Approach
2. Test Scenario
3. Test Condition and Expected Result (TCER)
4. Test Cycles Control Sheet (TCCS)
5. Test Script


Test Approach (First Step of any Test Stage)

Define details test stage based on Testing Strategy that defined in the Planning Stage.
Consists of
1. Test Overview- Test Objective
2. Stage Containment - Entry and Exit criteria
3. Test Environment
4. Test Tool


Test Scenario ( Part of Test Approach or TCER, no need separate deliverable)

Describe Functional or Technical area that need to be tested in High Level.
No Test Scenario for Component Test.

TCER
Action, Expected Result

Test Cycles Control Sheet (TCCS)
Define when and by whom, the test cycle are executed.
Used by Test Execution Team
Logical grouping of Test scenario and condition

Test Script
Consists of exact step of execution that Tester must follow.

Oscar Wilde

This few days, I search through articles in internet. I found some interesting quotes from Oscar Wilde, an Irish playwright, poet and author of numerous short stories and one novel.

Share with you guys some of the his quotes:

1. To be natural is such a very difficult pose to keep up.

2. Ordinary riches can be stolen, real riches cannot. In your soul are infinitely precious things that cannot be taken from you.

3. I have the simplest tastes. I am always satisfied with the best.

Pareto Principle

Today, I am studying Six Sigma from the skillSoft which I downloaded from myLearning. This is an interesting sharing about Pareto Principle.

Pareto Principle, also known as very famous rule- 80/20 rule, The law of vital few.

Pareto Principle is named after a famous Italy Economist- Pareto Vilfredo. He is the one observe 80 percent of income went to 20% of population.

However, in project management, we need to understand one thing- 20% effort to drive 80% of return.

In Computer Science, 20% of defeats cause 80% of error.

Occam's Razor

I learn this term in one of my Technology Architecture Concerns and Principles.
Always look for the simplest solution before you deep into the complicated one. This Occam's Razor principles also known as Law of Parsimony.

We should not make more assumptions than the minimum needed.

For instance, when you find your PC is slow, you do not make a lot of assumptions like your PC might affected by Trojan, OS corrupted, MSN problem and etc. You shud go for the minimum impact assumption- do a quick scan of your PC.

one should not increase, beyond what is necessary, the number of entities required to explain anything