Unit 26: Vocabulary

Please study the 20 vocabulary below and press the 'Mark Complete' button.
US
acceptance testing
determines if the requirements of a specification or contract are met
US
An acceptance test returns either as pass or fail, with a fail suggesting that there is a flaw present and the software should not go into production.
US
automated testing
the use of other tools and scripts to test the software you’re creating
US
Automated testing is often done with automation tools to execute test case suites.
US
black box testing
a method in which the internal structure is not known to the tester
US
Black box testing can be applied virtually to every level of software testing: unit, integration, system and acceptance.
US
build
a version of an application that is given by development team to the software testing team
US
A build, when tested and certified by the software testing team, is provided to the customers as “release”.
US
functional testing
ensures that the requirements of an application are satisfied
US
Functional testing is a kind of black box testing that is performed to confirm that the functionality of an application or system is behaving as expected.
US
integration testing
exposes faults in the interaction between integrated units
US
Integration testing is a level of software testing where individual units are combined and tested as a group.
US
manual testing
the process of finding defects or bugs without the aid of automation tools
US
A person with good attention to detail, who acts as an end user, should do manual testing to ensure the application's features behave correctly.
US
production
live version of a website or web application
US
Code that has undergone extensive development and testing before it is validated as production ready.
US
production error monitoring
sort of automated system that logs all errors in live code
US
Production error monitoring helps developers to monitor and fix crashes and other issues in real time, whenever they occur in the live version.
US
QA (Quality assurance)
ensures that the customer gets the best possible software
US
QA testers are primarily responsible for checking new software products, such as those for gaming systems, mobile or software applications, for defects, issues or bugs.
US
regression testing
confirms that a recent program or code change has not adversely affected existing features
US
Regression testing should be done before every release for all areas where changes have been made in the code.
US
release
the tested and verified version of a build
US
The release is the official launch of a version or application for the customers.
US
smoke testing
a test type to ensure that the most important functions work
US
The executed smoke tests qualified the build for further formal testing.
US
staging
a nearly exact replica of a production environment for software testing
US
A staging environment is a part of a workflow in most development projects and the deployment process.
US
system testing
a test of the complete and integrated software
US
The purpose of a system test is to evaluate the system's compliance with the specified requirements.
US
test case
a specification of the inputs, execution conditions & testing procedures
US
The process of developing test cases can also help find problems in the requirements or design of an application.
US
unit testing
the tests of individual components of a software
US
A unit is the smallest testable part of any software. It usually has one or a few inputs and usually a single output.
US
UX (user experience)
peoples emotions and attitudes about using a particular product, system or service
US
UX testing is the process of testing different aspects of user experiences to determine the best way for software and its elements to interact with its audience.
US
UI (user interface)
represents the cosmetics of the product
US
UI testing is the process of testing a product's graphical user interface to ensure it meets its pre-defined specifications.
US
white box testing
a method in which the internal structure is known to the tester
US
White box testing is a method of software testing that tests internal structures or workings of an application, as opposed to its functionality.
Go to unit menu