A.   User attemptation testing

B.   Unit testing

C.   System testing

D.   Integration testing

B.   white-box

C.   glass-box

D.   grey-box

A.   an old method of calculating the distance between two objects

B.   a principle or mechanism by which we can tell if the software is working according to someone’s criteria;

C.   No such thing!

A.   To assess whether the software is ready for release.

B.   To find faults in the software.

C.   To prove that the software is correct.

A.   Statements in the program

C.   Errors in the program

D.   Cycles in the program

B.   Its priority is very high and it needs to be handled immediately.

C.   The testing team is charged with seeing it through.

D.   It is technologically complex.

B.   True

A.   False

A.   Exercise the logical conditions in a program module

B.   Focus on testing the validity of loop constructs

C.   Rely on basis path testing

B.   Defect tracking

C.   Teamwork

D.   Configuration control

A.   Performance errors

C.   Typographical errors

D.   Logic errors

E.   Behavioral errors

B.   Neither of these

C.   Functionality, Reliability, Usability, Efficiency, Maintainability, Portability

A.   Tool used for non functional testing

B.   free ware open source tool

C.   web based testing tool

D.   above all

B.   Gray Box

C.   JUnit test

D.   Integration Testing

E.   Black Box

B.   Session-based testing is a software test method that involves the tester recording their behaviours to be reviewed at a later stage.

C.   Session-based testing is a software test method that aims to up skill junior testers who might not be as comfortable with the system under test.

D.   Session-based testing is a software test method that aims to combine speedy results with the expectations of an agile team.

B.   select test paths based on the locations and uses of variables

C.   exercise the logical conditions in a program module

D.   rely basis path testing

A.   Internal program design and code

B.   Requirements and functionality

C.   How an application functions under heavy loads

A.   Compatibility: most emulators are incompatible with popular versions of MS Windows.

B.   Installation issues: installing and handling emulators is more cumbersome than handling real hardware.

D.   Lack of reliability: emulators might not represent the user interface adequately.

A.   True

A.   Select test paths based on the locations and uses of variables

C.   Rely on basis path testing

D.   Focus on testing the validity of loop constructs

A.   Exception

C.   Beta

D.   Black Box

A.   Extreme Programming

C.   Agile Development

D.   Test Driven Development

A.   Usage Exploration

C.   Under Existence

D.   Usability Experience

A.   Incorrect or missing functions

C.   Interface errors

D.   Performance errors

E.   None of these

A.   Alpha tests are conducted by the user, while Beta tests are done by the testing team.

C.   Beta tests are conducted by the user, while Alpha tests are done by the testing team.

D.   Beta tests are done by the user under the supervision of the testing team at the test lab, while Alpha tests are done by the user in user's facilities without close supervision.

A.   A formal testing of the software

C.   An in-depth look into how the software functions

D.   None of these

B.   Severity is determined by the developers and business analysis, while priority - by the testing team.

C.   Priority is determined primarily by the technical factors, while Severity is determined by business-related factors.

D.   Severity is determined by user expectations, while Priority - by the impact on the functionality.

A.   Holistic Test Security Model

B.   Human Test Strategy Model

D.   High Tech Strategy Management

E.   Hollow Team Strategy Model

B.   A special type of Universal Resource Identifier (URI).

C.   Encryption that can protect the channel over which your conversation happens.

D.   A key-value pairs with an equals sign (=) between the key and the value.

A.   Plan - Act - Check - Do

C.   Plan - Check - Act - Do

D.   Plan - Check - Do - Act

B.   Performance

C.   Black Box

D.   Functionality

B.   Developers

C.   Customer Support

D.   Test Engineers

B.   Detective control

C.   Quality control

D.   Corrective control

A.   A process in which the tests only takes boundary values for testing

A.   A reader

B.   A recorder

D.   A moderator

A.   Suggesting a release schedule.

C.   Making the decision whether to release the system-under-test into production.

D.   Playing user's advocate by questioning design decisions.

B.   The need for stub programs is eliminated.

C.   Test conditions are easier to create.

D.   Observation of test results is easier.

A.   Inability to read data off the app fields.

C.   Inability to compare images.

D.   Inability to automate clicking app objects and make dropdown selections.

A.   The procedure is what must happen and the process is the step-by-step of how it will happen

B.   The procedure is who executes the necessary testing and the process is when it will be executed

C.   The process is who executes the necessary testing and the procedure is when it will be executed

A.   Configuration Control Board

B.   Software Development Team

D.   Customer Liaison

B.   Defects are logged by Test Engineers, while Change Requests - by Business Analysts.

C.   They are handled by different logging systems.

D.   Defects always have a risk associated with their resolution, while Change Requests do not.

A.   Beta Testing

B.   Alpha Testing

D.   System Testing

E.   Integration Testing

A.   True

A.   Delivered on time

B.   Meets requirements and expectations

C.   Delivered within budget

B.   Glass Box Technique

C.   White Box Technique

B.   Security testing

C.   Functional testing

D.   Performance testing

A.   Subversion

B.   Git

C.   CVS

B.   Testing the effected modules after the bug fixed

C.   Without fixed If we test Defect Again

A.   Deal only with interfaces.

B.   Focus on system's behavior under stress.

D.   Are well-documented and easy to execute manually.