Key Words Flashcards
Relate directly to a specific requirement or user story. They are either part of the detailed description or an attribute of the related requirement. Measurable and can be True or False. Can be used to check whether a requirement or user story has been implemented as expected
Acceptance Criteria
Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.
Acceptance Testing
An item or element that must be included in a change being implemented as part of a testing effort. Can be Product or Business related and are part of the Acceptance Criteria process. They are also included within a User Story
Requirement
Is typically comprised of a set of requirements and similar to a requirement; it is also part of the Acceptance Criteria process
User Story
Form of acceptance testing that is often used for Commercial Off-the-Shelf Software (COTS) or for Software as a Service (SaaS) platforms. It is conducted to
obtain feedback from the market after development and inhouse testing are completed.
Beta testing
Leverages the tester’s experience, knowledge and
intuition
Experience-based test technique
Test technique that is not based
on detailed predefined test procedures, all activities are carried out within an uninterrupted period of time called a session. The testers are domain experts. They are familiar with user needs, requirements and business processes, but they are not
necessarily familiar with the product under test.
Exploratory testing
Utilizes the structure: “Given – When – Then” for automated script creation
Keyword-driven
testing
Scenario created based on acceptance criteria; full coverage is ideal
Test case
The extent to which each test case meets the acceptance testing objectives and as many scenarios are accounted for as possible
Coverage
Testing approach that can
also be combined with keyword-driven testing and data-driven testing approaches
Model-based testing
An essential part of providing a “good
experience” for users when they use their applications on a variety of fixed and mobile platforms. Characteristics include: time-behavior, resource utilization, capacity
Performance efficiency
Characteristics include: confidentiality, Integrity, Non-repudiation, Accountability, Authenticity. The extent to which something is safe
Security
Characteristics include: appropriateness recognizability, learnability, operability, user error protection, user interface aesthetics, accessibility
Usability
The degree to which a product or system can be used by specified users to achieve specified goals with effectiveness, efficiency and
satisfaction in a specified context of use. Can either be specified or measured as a product quality characteristic in terms of its sub-characteristics, or specified or
measured directly by measures that are a subset of quality in use
User experience
