user test

A test whereby real-life users are involved to evaluate the usability of a component or system.

user story testing

A black box test design technique in which test cases are designed based on user stories to verify their correct implementation. See also user story.

user story

A high-level user or business requirement commonly used in agile software development, typically consisting of one or more sentences in the everyday or business language capturing what functionality a user needs, any non-functional criteria, and also includes acceptance criteria. See also agile software development, requirement.

user scenario testing

See use case testing

user-based quality

A view of quality, wherein quality is the capacity to satisfy needs, wants and desires of the user(s). A product or service that does not fulfill user needs is unlikely to find any users. This is a context dependent, contingent approach to quality since different business characteristics require different qualities of a product. [after Garvin] See also manufacturing-based quality, product-based quality, transcendent-based quality, value- based quality.

user acceptance testing

ISTQB Glossary  definition

Acceptance testing carried out by future users in a (simulated) operational environment focusing on user requirements and needs.

See acceptance testing.

Note:
The explanation for this term is included in the explanation for acceptance testing 

use case testing

A black box test design technique in which test cases are designed to execute scenarios of use cases.

use case

A sequence of transactions in a dialogue between an actor and a component or system with a tangible result, where an actor can be a user or anything that can exchange information with the system.

usability testing

Testing to determine the extent to which the software product is understood, easy to learn, easy to operate and ractive to the users under specified conditions. [After ISO 9126]

usability

The capability of the software to be understood, learned, used and ractive to the user when used under specified conditions. [ISO 9126]

Unreachable code

ISTQB Glossary definition In Simple English, Field Notes For

ISTQB Glossary  definition 

Code that cannot be reached and therefore is impossible to execute.

In Simple English,

 
Parts of the software that cannot be tested because there is no way to run the code that was written for those parts.

Field Notes

• The discussion about unreachable code arises only when you as the testing team have access to code.
• This means that only when doing a white box or glass box testing is when you can encounter 'Unreachable code'
• Unit testing is another scenario where 'Unreachable code' can be encountered.
• There is a difference between a screen element or feature not working and 'Unreachable code'
• 
  

For Example:

Say for example,

You are testing an software which has a feature to print some reports as PDF documents you can save to the computer.

Say there is also a business rule that is coded in the sofrware that users are allowed to save reports as PDF to the computer only when the report has more than 10 pages.

Say there is un editable default in all the reports that they generated as single page reports.

Now, there is no possible way the “print as PDF” feature will be called, so that become unreachable code.

of reports.and that piece of code to print gets called only when the number of copies being printed is two and you application does not have an feature to change the number of copies to be prineted and defaults the number of copies to one. Now the feature to print PDF is never going to get called and its code is unreachable.

unit testing

See component testing.

unit test framework

A tool that provides an environment for unit or component testing in which a component can be tested in isolation or with suitable stubs and drivers. It also provides other support for the developer, such as debugging capabilities. [Graham]

unit

See component.

understandability

The capability of the software product to enable the user to understand whether the software is suitable, and how it can be used for particular tasks and conditions of use. [ISO 9126] See also usability.

U

U

Understandability

ISTQB Glossary  definition 

"The capability of the software product to enable the user to understand whether the software is suitable, and how it can be used for particular tasks and conditions of use. [ISO 9126] See also usability."

In Simple English,

An measure of how easy a software is to understand (not use) for a targeted user.


Field Notes
1. This is not an very common way of measuring a system being built. "Usability" is usually used instead.

2. Usability however is not exactly same  same as "Understandability"

3. May be this is because, in most cases, "Usability" is considered more important than "Understandability" of a system.
 
Say for example you have new car that is being designed, the focus is always on to making it easy for the driver and passengers to use the car not to make them understand how it works.

4.  That said, please note that in some special cases, "Understandability" will trump usability depending on need. This is more in cases where multiple people will use the system at multiple point of time without much prior training.

For Example:

Think about a airplane  simulator, the purpose of it is for the person using it to understand how plane is flown/operated. beyond the objective of training, It does not matter how easy it is to operate it.

However, when you think of an actual plane built for being flown, it will matter more that the people operating it find it easy to use.

Unit testing

See component testing.

Unreachable code

Code that cannot be reached and therefore is impossible to execute.

Usability

The capability of the software to be understood, learned, used and attractive to the user when used under specified conditions. [ISO 9126]