white-box technique

See white-box test design technique.

Work Breakdown Structure

ISTQB Glossary definition explanined in simple english with examples based on real experiance fot the testing term “ Work Breakdown Structure”.

ISTQB Glossary definition

An arrangement of work elements and their relationship to each other and to the end product.

[CMMI]

In Simple English,this means
A list of tasks identified to complete an end product.

QA Practitioner’s notes for real work experience in this field

• While this is simple enough to maintain for small projects, it is a complicated list to maintain for a bigger project.
• Tasks are usually identified and provided by the team for better ownership o  2

Now, Let’s see one or more example cases to understand this even better:
your Feedback
So, what do you think?
Was the explanation clear enough?
Did you understand?
Did you get what you were searching for?
In an effort to explain these terms as simple as it could be i go through rigorous cycles of writing, reviewing and updating the post till it is simple enough.Meanwhile,
Please leave your comments,questions & opinions about this testing term explained here or this site in general below. i would love to know.

If you have any more questions, comments or compliments please let me know as your comments below.

v0.1

W

W - Click on the words below, to learn and understand them easily

Walkthrough - F, ATM

WAMMI - ATA

WBS

Website Analysis and MeasureMent Inventory (WAMMI) - ATA

White-box technique

white-box test design technique - F, ATT

white-box testing - F

Wide Band Delphi - ATM

wild pointer - ATT

Work Breakdown Structure

wild pointer

ISTQB Glossary definition In Simple English, Field Notes For wild pointer

ISTQB Glossary definition

A pointer that references a location that is out of scope for that pointer or that does not exist.

See also pointer.

In Simple English,

An address to no where.

Field Notes

For Example:

Please leave your comments,questions & opinions about this testing term explained here or this site in general below. i would love to know.

white-box testing

ISTQB Glossary  definition 

"Testing based on an analysis of the internal structure of the component or system."

In Simple English,
it is testing done with complete information and knowledge of how the internals of the component or system under test works available and used by the tester.

Field Notes 

1. This is also called Glass box testing. Glass box because the tester can see what is inside.
2. Often people assume it as knowing the code and testing. It is not often the case. 
3. Testing the code directly is part of unit testing and not strictly a functional test in the broad sense of software projects.
4. This is still a functional test.
5. This testing needs the tester to be proficient  with the internal structure of the system under test.
6. Getting help from a developer does not count as a white box testing as more often the lack of knowledge and understanding undermines the test objective.
7. 
   

For Example:

white-box test design technique

ISTQB Glossary  definition 

"Procedure to derive and/or select test cases based on an analysis of the internal structure of a component or system."

In simple English:

In essence, you as a tester will know the internal working of what you are testing. 

Your test design and execution will be based on your knowledge and understanding of the code being tested. 

Field Notes 

1. It's very easy to understand this, if you read it as transparent box testing. 

2. The tester in this case will have to be comfortable with technology used to build the system being tested. 

3. More than comfort, tester being competent in the technology is essential. 

4. Usually mission critical systems and systems that have a huge impact in terms of money involved our time is tested this way. 

5. Products that are built to be the foundation for lot more things in the future are tested like this. 

For Example:
Say, you want to test the software that controls an rocket. What you need to be sure of its that there is no piece of code that might bring the rocket down. 

Website Analysis and MeasureMent Inventory (WAMMI)

A questionnaire-based usability test technique for measuring web site software quality from the end users point of view.

WBS

See Work Breakdown Structure.

WAMMI

See Website Analysis and MeasureMent Inventory.

walkthrough

A step-by-step presentation by the author of a document in order to gather information and to establish a common understanding of its content. [Freedman and Weinberg, IEEE 1028] See also peer review .

Walkthrough

A step-by-step presentation by the author of a document in order to gather
information and to establish a common understanding of its content. [Freedman and
Weinberg, IEEE 1028]

White box testing

Testing based on an analysis of the internal structure of the component or
system.

Wide Band Delphi

ISTQB Glossary definition explained in simple english with examples based on real experience for the testing term “ Wide Band Delphi"

ISTQB Glossary definition

An expert based test estimation technique that aims at making an accurate estimation using the collective wisdom of the team members.

In Simple English, this means 

just ask the team how much time testing will take and use it.

QA Practitioner’s notes for real work experience in this field

• So who is this ‘Expert’?
  • ‘Expert’ here means someone who has prior experience with the testing that is being estimated.
  • An  interesting question such a definition brings is: what is no one has never tested the test being estimated?
  • In such case, the team with prior similar experience is a better ‘Expert’.
  • Even better is to ask the actual team that will eventually test the application to be used as the ‘Expert'
• ‘Collective Wisdom’ is the emphasis here. 
  • This means that the first step is to ask each member of the test team separately  for their estimate. 
  • Most important distinction here is to ask without suggesting a baseline.
  • So, the question should not be “Can this be tested in a week?” Or “How much time should we take to test this?"
  • The question should be open ended and directed to just the person being asked. Something like “How much time do YOU think testing this release/version will take?"
  • Another distinction here is not to ask, how much time will you need to test this? This becomes a incorrect question as it forces the person to answer for only what they assume as the part they will be testing.
  • The objective is to not that. it is ask each team member how much time they think will be needed to test the release/version. 
• It is what the team thinks it will take to get the job done.
• Please Remember.  This is still an estimation. Just because it comes from the team it does not some how qualify to become a better estimate in anyway. 
• Most times, the test engineers do not include time for test lead / test manager level tasks like triage, reporting and meetings.

• The unit varies.  
  • This is becase every person may express it in a different way.
  • Some. might say, may a week. Some may say, 5 days. some may say it as we can run 14 test cases.
• Prepare to be surprised, there may be a wide band of estimates. 
  • Some may say "hmm., just 4 days. we can get this done?"
  • Someone in the same team for the same release may at the same time say “this will definetly take 4 weeks at the minimum"
  • Hence the “Wide” i guess.

Now, Let’s see one or more example cases to understand this even better:

Most often, i have seen this method used even without the awareness that the team is using this method.

Case 1:
An emergency release is being planned to address some priority issues. Most cases have much tighter deadlines. The test team gets asked this question “So, how much time do you need to get this tested?"

Feedback
So, what do you think?
Was the explanation clear enough?
Did you understand?
Did you get what you were searching for?

If you have any more questions, comments or compliments please let me know as your comments below.