random Flashcards
is the testing of “how well the system behaves”.
-Non-functional testing
It is sometimes appropriate to start early in the life cycle (e.g., as part of reviews and component testing or system testing).
for non-functional testing
the degree to which the set of functions covers all the specified tasks and user objectives
Functional completeness
Key Focus: Ensuring the system has all the required features and functionalities for task completion.
sometimes needs a very specific test environment, such as a usability lab for usability testing.
-Non-functional testing
-The degree to which a component or system uses time, resources and capacity when accomplishing its designated functions.
Performance efficiency
(non-functional software quality characteristics)
The degree to which a component or system provides the correct results with the needed degree of precision.
Functional correctness
Key Focus: Verifying that the system behaves as expected, performing tasks accurately and delivering correct outcomes.
-The degree to which a component or system can exchange information with other components or systems, and/or perform its required functions while sharing the same hardware or software environment.
Compatibility
(non-functional software quality characteristics)
-The degree to which a component or system can be used by specified users to achieve specified goals in a specified context of use.
Usability
(non-functional software quality characteristics)
The degree to which the functions facilitate (make easier) the accomplishment of specified tasks and objectives
Functional appropriateness:
Key Focus: How well the functions of the system align with user needs and simplify task completion.
-The degree to which a component or system performs specified functions under specified conditions for a specified period of time.
Reliability
(non-functional software quality characteristics)
-The degree to which a component or system protects its data and resources against unauthorized access or use and secures unobstructed access and use for its legitimate users.
Security
(non-functional software quality characteristics)
-The degree to which a component or system can be modified by the intended maintainers.
Maintainability
(non-functional software quality characteristics)
-The degree to which a component or system can be transferred from one hardware, software or other operational or usage environment to another.
Portability
(non-functional software quality characteristics)
with real users testing the system in realistic scenarios to evaluate ease of use.
usability lab
-when time or money is short when fixing defects, this might be restricted to simply exercising the steps that should reproduce the failure caused by the defect and checking that the failure does not occur.
confirmation testing
-confirms that no adverse consequences have been caused by a change, including a fix that has already been confirmation tested.
regression testing
-It is advisable first to perform an impact analysis to optimize the extent of this testing
Regression testing
-It is advisable first to perform an impact analysis to optimize the extent of this testing
Regression testing
Impact analysis may be done before a change is made, to help decide if the change should be made, based on the potential consequences in other areas of the system
maintenance testing
it can be corrective
adaptive to changes in the environment
improve performance or maintainability
maintenance categories
Testing the changes to an operational system or the impact of a changed environment to an operational system.
maintenance testing
-These adverse consequences could affect the same component where the change was made, other components in the same system, or even other connected systems.
regression testing
-can involve planned releases/deployments and unplanned releases/deployments (hot fixes).
maintenance testing
refer to specific attributes or features of a product, system, or service that define its overall quality.
Quality characteristics
-often requires specific support, such as test harnesses or unit test frameworks.
component testing
refers to the activities involved in updating, modifying, or enhancing a software system after it has been deployed or delivered.
Maintenance
illustrate the order of interactions between components or objects in the system, showing how they collaborate to complete a function.
Sequence diagrams
this testing may not be restricted to the test object itself but can also be related to the environment.
Regression testing
Interfaces define how components communicate with each other, while communication protocols dictate the rules for data exchange
Interface and Communication Protocol Specifications
describe functional scenarios from the user’s perspective, showing how different parts of the system interact to fulfill business requirements.
Use cases
define how the system interacts with external systems
External interfaces
The process of modifying a component or system after delivery to correct defects, improve quality characteristics, or adapt to a changed environment.
maintenance
Testing based on an analysis of the specification of the component or system.
Black-box testing
Synonyms: specification-based testing
specification-based and derives tests from documentation external to the test object.
Black-box testing
-main objective is checking the system’s behavior against its specifications.
Black-box testing
Supports both Functional and nonfunctional testing
All the four test types(Functional testing, Non-functional testing, Black-box testing, White-box testing) can be applied to all test levels,
A TEST LEVEL that focuses on determining whether to accept the system. See also: user acceptance testing
acceptance testing
-Ideally, this test should be performed by the intended users.
acceptance testing