Check Your Qa Level With Online Quiz

All test cases should be automated

Test cases should be reviewed and updated regularly

Test Team should be changed for each major release

You should not even try to avoid Pesticide paradox

All issues should be checked according to Definition of Done

Attach *.doc file with inserted image

Attach *.pdf file with inserted image

Attach standalone *.jpg or *.png image

Attach *.xls file with inserted image

Attach only *.html file

Attach whole webpage

Testers

End-users

Customers

Developers

Error managers

Only Good Test Cases should be executed.

Test Cases written by good test engineers should be executed.

Testing should be on the basis of Risk

Only few tests should be run

Independent Testers cannot identify defects.

Independent Testers can test better than developers

Independent testers see other and different defects and are unbiased.

Independent testers are much more qualified than Developers

A type of software testing which verifies that software, which was previously developed and tested, still performs correctly after it was changed or interfaced with other software.

A type of testing ensures that your application can gracefully handle invalid input or unexpected user behaviour.

A level of the software testing where a complete and integrated software is tested.

A type of testing that ensures new version of the product to continue to work with the older product

A type of software testing that comprises a non-exhaustive set of tests that aim at ensuring that the most important functions work.

Grey box

Blue box

Black box

White box

A type of testing ensures that your application can gracefully handle invalid input or unexpected user behaviour.

Testing a system with a significant load extended over a significant period of time, to discover how the system behaves under sustained use.

A type of testing that ensures new version of the product to continue to work with the older product

A type of software testing which verifies that software, which was previously developed and tested, still performs correctly after it was changed or interfaced with other software.

A type of software testing that comprises a non-exhaustive set of tests that aim at ensuring that the most important functions work.

Black-box testing

Performance testing

Smoke testing

Regression testing

Acceptance testing

It signals when the testing should complete and when should the product be ready to release

It signals when the product should complete and when should the testing start

A process that should run when a system stop and the testing starts

A process that should run when a system begins

It is a test case design technique in which testers have to create the defects that might occur and write bugs to represent them.

It is a test case design technique in which testers have to guess the defects that might occur and write test cases to represent them.

It is the process of adding known bugs in a program for the tracking the rate of detection & removal.

It is the process of adding unknown bugs in a program for the tracking the rate of detection & removal.

A QA engineer is supposed to understand software internal operating system, its structure and implementation

It is necessary to check all the software code paths

QA engineer is not supposed to understand the internal workings of the software

It is necessary to check software functional requirements

Black Box Testing

White Box Testing

Static Testing

Dynamic Testing

It covers the core functionality of a product like standard business flows.

It is related to user interface (UI) in the application.

It is related to all functions in the application.

It covers all functionality of a product like standard business flows.

White Box Techniques.

Experience Based Techniques.

Glass Box Techniques.

Black Box Techniques.

Miscommunication.

Programming errors.

Change in requirements.

Software complexity.

Code development

Tests development

Tests execution

Code execution

None of above

Absence of bugs does not prove that the program functions correctly

Testing should start as early as possible

Exhaustive testing is possible in most cases

Code coverage level does not prove product quality

Hire third party independent verification and validation

Assign internal staff members that are not involved in validation and verification activities

All options are correct

Independent evaluation

It specifies which bug should get fixed first.

It describes the application point of view.

It represents the gravity/depth of the bug.

It defines the user’s point of view.

Acceptance testing

Usability testing

System/end-to-end testing

Integration testing

Configuration Testing

Grey box

Sanity

Smoke

User interface

Get promise from developers not to do bugs anymore

Write a test case for the production defect and include it in the regression suite

Won't release this functionality anymore

Test it every day after production release

To know when a specific test has finished its execution

To ensure that the test case specification is complete

To set the criteria used in generating test inputs

To know when test planning is complete

To plan when to stop testing

Re-testing is running a test again; regression testing looks for unexpected side effects

Re-testing looks for unexpected side effects; regression testing is repeating those tests

Re-testing is done after faults are fixed; regression testing is done earlier

Re-testing uses different environments, regression testing uses the same environment

Re-testing is done by developers, regression testing is done by independent testers