Software Engineering Quiz 3

Which of the following are issues that make real-time testing difficult? A)Limited device processing capacity B)Power limitations on the device C)Unique mobile network infrastructures D) all of the above

All of the above

Which of following is not one of the elements that need to be considered when constructing WebApp server-side configuration tests?

Browser compatibility

Which test case design technique(s) are appropriate for WebApp component-level testing? A)Boundary value analysis B)Equivalence partitioning C)Path testing D)All of the above

D) All of the above

Which of the following are characteristics of testable software? A)observability B)simplicity C)stability D)all of the above

D) all of the above

The overall strategy for interface testing is to uncover errors A)in navigation semantics B)in overall usabililty C)related to specific interface mechanisms D)both a and c

D) both a and c

Regression testing should be a normal part of integration testing because as a new module is added to the system new A)control logic is invoked B)data flow paths are established C)drivers require testing D)all of the above E)a and b

E) a and b

Which of the following strategic issues needs to be addressed in a successful software testing process? A)conduct formal technical reviews prior to testing B)specify requirements in a quantifiable manner C)use independent test teams D)wait till code is written prior to writing the test plan E)a and b

E) a and b

Black-box testing attempts to find errors in which of the following categories A)incorrect or missing functions B)interface errors C)performance errors D)none of the above E)a, b, c

E) a, b, c

Which of that following add to the difficulty of testing MobileApp gestures? A)Automatic tool use is difficult B)Creating functions to simulate events C)Screen size variation D)Using paper prototypes E)a, b, c

E) a, b, c

Which of the following is an approach to debugging? A)backtracking B)brute force C)cause elimination D)code restructuring E)a, b, c

E) a, b, c

Integration testing of object-oriented software can be accomplished by which of the following testing strategies? A)Cluster testing B)Glass-box testing C)Thread-based testing D)Use-based testing E)a, c, d

E) a, c, d

What types of errors are missed by black-box testing and can be uncovered by white-box testing? A)behavioral errors B)logic errors C)performance errors D)typographical errors E)b and d

E) b and d

As the WebApp architecture is constructed which types of testing are used as integration tests? A)Component testing B)Content testing C)Navigation testing D)Usability testing E)both a and c

E) both a and c

Which of the following are reasons for testing in the wild? A)Assessing the impact of production environments B)Failing to create test cases C)Not understanding user demographics D)Testing for variable performance on user devices E)both a and d

E) both a and d

Which of the following need to be assessed during unit testing? A)algorithmic performance B)code stability C)error handling D)execution paths E)c and d

E) c and d

Top-down integration testing has as it's major advantage(s) that A)low level modules never need testing B)major decision points are tested early C)no drivers need to be written D)no stubs need to be written E) b and c

E)b and c

A weighted device platform matrix helps to prioritize test cases.

False

Automated testing tools eliminate the need to do regression testing for MobileApps.

False

Boundary value analysis can only be used to do white-box testing.

False

Configuration reviews are not needed if regression testing has been rigorously applied during software integration.

False

Continuous speech recognition techniques have eliminated the need for key entry in MobileApps.

False

Database testing is very rarely a part of WebApp content testing.

False

Device emulators eliminate the need to test MobileApps on actual devices.

False

Documentation does not need to be tested.

False

Encapsulation of attributes and operations inside objects makes it easy to obtain object state information during testing.

False

Graph-based testing methods can only be used for object-oriented systems

False

In software quality assurance work there is no difference between software verification and software validation. (T/F)

False

It is not possible to test object-oriented software without including error discovery techniques applied to the system OOA and OOD models.

False

Multiple class testing is too complex to be tested using random test cases.

False

Performance testing is only important for real-time or embedded systems.

False

Program flow graphs are identical to program flowcharts.

False

Recovery testing is a system test that forces the software to fail in a variety of ways and verifies that software is able to continue execution without interruption.

False

Since MobileApp users are attracted to new technologies they are very tolerant of errors and testing effort can be reduced.

False

Software validation is achieved through a series of tests performed by the user once the software is deployed in his or her work environment.

False

Stress testing examines the pressures placed on the user during system use in extreme environments.

False

Test planning is not used in WebApp testing.

False

Testing MobileApps is not different than testing WebApps

False

The Testing across borders is not necessary each MobileApp is developed for use in a specific country.

False

The correctness of the OOA and OOD model is accomplished using formal technical reviews by the software quality assurance team.

False

The purpose of WebApp navigation syntactic testing is to ensure the correct appearance of each navigation mechanism.

False

Units and stubs are not needed for unit testing because the modules are tested independently of one another.

False

Usability tests should be designed and executed by intended users for a given WebApp.

False

WebApp compatibility testing is conducted to be sure that the user model for usage scenario matched the user category assigned to a given user.

False

When testing object-oriented software it is important to test each class operation separately as part of the unit testing process.

False

With thorough testing it is possible to remove all defects from a program prior to delivery to the customer.

False

Which of the following is not a WebApp interface mechanism?

Forms

Which of the following is not one of the objectives of WebApp content testing?

Identify linking errors

Which of the following is not one of the dimensions of quality used to assess a WebApp?

Maintainability

Load testing involves determining the input of which 3 variables?

N, T, D

Which of the following is not a testable WebApp security element?

Penetration

Both Web engineers and non-technical users conduct navigation semantics testing for WebApps.

True

By collecting software metrics and making use of existing software reliability models it is possible to develop meaningful guidelines for determining when software testing is done.

True

Debugging is not testing, but always occurs as a consequence of testing.

True

Designing test cases directly from user stories increase the likelihood of developing effective test cases in a timely manner.

True

Equivalence testing divides the input domain into classes of data from which test cases can be derived to reduce the total number of test cases that must be developed.

True

MobileApps require special testing methodologies because of concerns associated using them in diverse network environments.

True

Orthogonal array testing enables the test designer to maximize the coverage of the test cases devised for relatively small input domains.

True

Part of the reason for stress testing is to ensure that the MobileApp exhibits graceful degradation on failure.

True

Predictive technologies are often used to help speed up virtual keyboard inpu on mobile devices.

True

Random order tests are conducted to exercise different class instance life histories.

True

Security testing attempts to verify that protection mechanisms built into a system protect it from improper penetration.

True

Since WebnApps evolve continuously, the testing process is an on-going activity, conducted by the Web support staff using regression tests.

True

Since many WebApps evolve continuously, the testing process must be ongoing as well.

True

Test case design for OO software is driven by the algorithmic detail of the individual operations.

True

The ability of a MobileApp to handle alerts without disrupting user workflow must be tested in the production environment?

True

The consistency of object-oriented models may be judged by reviewing the CRC card model.

True

The cyclomatic complexity of a program can be computed directly from a PDL representation of an algorithm without drawing a program flow graph.

True

The focus of validation testing is to uncover places that s user will be able to observe failure of the software to conform to its requirements.

True

The state model can be used to derive test cases based on the dynamic behavior of an object-oriented system.

True

To design client-side configuration tests each user category is assessed to reduce the number of configuration variables to a manageable number.

True

Use-cases can provide useful input into the design of black-box and state-based tests of OO software.

True

Validation of object-oriented software focuses on user visible actions and outputs from the system.

True

WebApp stress testing is a continuation load testing.

True

WebApps require special testing methodologies because WebApp errors have several unique characteristics.

True

When testing WebApp interface semantics, each use-case is used as input for the design of a testing sequence.

True

When testing the quality of user interaction the focus should be on user visible interaction mechanisms.

True

WebApp performance tests are designed to

asses WebApp usability

The testing technique that requires devising test cases to demonstrate that each program function is operational is called

black-box testing

Scenario-based testing

concentrates on actor and software interaction

Acceptance tests are normally conducted by the

end users

Which of these techniques is not useful for partition testing at the class level

equivalence class partitioning

Condition testing is a control structure testing technique where the criteria used to design test cases is that they

exercise the logical conditions in a program module

Loop testing is a control structure testing technique where the criteria used to design test cases is that they

focus on testing the validity of loop constructs

The OO testing integration strategy involves testing

groups of classes that collaborate or communicate in some way

The cyclomatic complexity metric provides the designer with information regarding the number of

independent logic paths in the program

Bottom-up integration testing has as it's major advantage(s) that

no stubs need to be written

Fault-based testing is best reserved for

operations and classes that are critical or suspect

Smoke testing might best be described as

rolling integration testing

Data flow testing is a control structure testing technique where the criteria used to design test cases is that they

select test paths based on the locations and uses of variables

Test derived from behavioral class models should be based on the

state transition diagram

The best reason for using Independent software test teams is that

the conflicts of interest between developers and testers is reduced

Real-time applications add a new and potentially difficult element to the testing mix

time

What is the normal order of activities in which traditional software testing is organized?

unit testing, integration testing, validation testing, system testing

The testing technique that requires devising test cases to exercise the internal logic of a software module is called

white-box testing