NEW
Font size
WorksheetsTesting and Evaluation
Total questions: 19
Worksheet time: 10mins
Internal system testing using live test data can be best described as:
white box testing.
black box testing.
alpha testing.
beta testing.
The main purpose of the testing and evaluation stage of the software development cycle is to:
discover bugs in the source code, at both the module and program level.
ensure the program operates correctly with live test data.
train users in the operation of the new product.
ensure the product meets its requirements and design specifications.
Explicit knowledge of the internal workings of an item is utilised when performing:
white box testing.
black box testing.
alpha testing.
beta testing.
System-level testing should include all components of the system. This includes:
modules, programs and systems.
hardware, software, data, personnel and procedures.
large file sizes, mix of transaction types, response times, and volume data.
Benchmarking is
used to ensure the product is of a high quality.
a technique used to isolate and report weaknesses in the product.
used to compare a product to other, similar products using a standard point of reference
intended to gauge the extent to which a product has realised its goals and objectives.
Users testing a software product before final release are participating in:
white box testing
beta testing.
black box testing.
alpha testing.
The inputs and expected outputs are known, however the details of the processes that transform inputs into outputs are unknown during:
black box testing.
alpha testing.
white box testing.
Large files are likely to highlight problems in regard to:
errors in the logic of the source code.
the operation of the user interface.
inefficient or processor intensive operations.
Tests in regard to response times are formulated to primarily test the:
operation of the user interface.
hardware components of the system.
procedures required when operating the new product
product compared to competitors’ products
Which of the following is NOT true in regard to Quality Assurance (QA)?
QA practices should be implemented throughout the development process.
QA is primarily about ensuring customers’ expectations are realised in the final product.
QA ensures testing of software products results in error-free applications.
QA standards are available for implementation by businesses. Certification allows use of standards logos.
Testing is carried out during which stage of the software development cycle?
Planning and design.
Implementation
Testing and evaluation.
All of the above.
CASE tools used during the "testing evaluation" stage:
are used to automate tedious and repetitious tasks.
provide a means of producing system models.
assist developers in the construction of code
ensure design specifications remain consistent across the application.
Customised off-the-shelf (COTS) packages can greatly simplify and shorten the software development process. Testing of software based on COTS packages can be difficult because:
differing versions of the COTS package may cause changes and/or problems to the product.
errors in the COTS package cannot generally be rectified by the software developer.
other products that use the services of the COTS package can affect functionality in unexpected ways.
All of the above.
The difference between live test data designed to test large file sizes and that designed to test volume data is:
large file sizes test the ability of the software to retrieve data; volume data tests the ability of the software to process large amounts of input simultaneously
large file sizes test the ability of the software to process data correctly; volume data tests the ability of the software to process large amounts of data
large files ensure the product is robust in design; volume data ensures logic errors are identified.
large file sizes can cause arithmetic overflow errors which must be identified; volume data is used to test the user interface.
Why should program test data be used again during system testing?
It is easier than producing new test data sets.
Problems identified during system testing are the same as those identified during program testing.
The outputs from both tests can be compared. Differences will highlight system issues compared to program issues.
The expected outputs are known, hence correcting any errors will be straightforward.
Live test data:
ensures the logic of source code is error free.
is used to test the operation of the system under extreme conditions.
is only used during beta testing.
can be used most effectively once the program has been distributed.
CASE tools that can simulate the activities of a large number of users are used for:
functional testing.
load testing.
test data generation.
communicating test results.
Documentation should be created throughout the testing process. The major purpose of this documentation is to:
justify the costs of the testing process.
provide evidence to support the recommendations
involve testers in the development of the product.
ensure that the integrity of the testing process is maintained.
Communicating test results effectively is crucial to the testing operation. Why?
This is the means by which recommendations will be put into practice.
The significance of problems must be made clear
Problems not corrected now will prove more costly to correct once the product has been distributed.
All of the above.
