0

testing Online Quiz - 139

Description: testing Online Quiz - 139
Number of Questions: 20
Created by:
Tags: testing
Attempted 0/20 Correct 0 Score 0

During which test activity could faults be found most cost effectively?

  1. Execution

  2. Design

  3. Planning

  4. Check Exit criteria completion


Correct Option: C

Verification is

  1. Checking that we are building the right system

  2. Checking that we are building the system right

  3. Performed by an independent test team

  4. Making sure that it is what the user really wants


Correct Option: B

Cyclomatic Complexity method comes under which testing method

  1. White box

  2. Black box

  3. Green box

  4. Yellow box


Correct Option: A

Which of the following is the odd one out?

  1. White box

  2. Glass box

  3. Structural

  4. Functional


Correct Option: D

What is the main difference between a walkthrough and an inspection?

  1. An inspection is lead by the author, whilst a walkthrough is lead by a trained moderator.

  2. An inspection has a trained leader, whilst a walkthrough has no leader.

  3. Authors are not present during inspections, whilst they are during walkthroughs.

  4. A walkthrough is lead by the author, whilst an inspection is lead by a trained moderator.


Correct Option: D

AI Explanation

To answer this question, you need to understand the definitions and characteristics of a walkthrough and an inspection. Let's go through each option to understand why it is correct or incorrect:

Option A) An inspection is led by the author, whilst a walkthrough is led by a trained moderator. This option is incorrect. In a walkthrough, the author typically guides the session, while in an inspection, a trained moderator or inspector leads the process.

Option B) An inspection has a trained leader, whilst a walkthrough has no leader. This option is incorrect. Both a walkthrough and an inspection typically have a leader or facilitator who guides the process.

Option C) Authors are not present during inspections, whilst they are during walkthroughs. This option is incorrect. Authors may or may not be present during both walkthroughs and inspections. The presence of authors can vary depending on the specific context or purpose of the walkthrough or inspection.

Option D) A walkthrough is led by the author, whilst an inspection is led by a trained moderator. This option is correct. The main difference between a walkthrough and an inspection is that in a walkthrough, the author typically leads the session, while in an inspection, a trained moderator or inspector leads the process.

Therefore, the correct answer is Option D. A walkthrough is led by the author, whilst an inspection is led by a trained moderator.

The cost of fixing a fault

  1. Is not important

  2. Increases as we move the product towards live use

  3. Decreases as we move the product towards live use

  4. Is more expensive if found in requirements than functional design

  5. Can never be determined


Correct Option: B
Explanation:

To understand the question, the user needs to know that the cost of fixing a fault refers to the amount of money and resources that are required to correct an error or mistake in a product or system. It is important to minimize the cost of fixing faults in order to create a high-quality product that is efficient and effective.

Now, let's go through each option and explain why it is right or wrong:

A. Is not important: This option is incorrect. The cost of fixing a fault is important because it affects the overall quality and cost of the product. The more faults that need to be fixed, the greater the expense and the longer it will take to develop and release the product.

B. Increases as we move the product towards live use: This option is correct. As a product moves closer to live use, the cost of fixing faults increases. This is because the product is closer to being released to the public, and any faults or issues that are discovered at this stage will require more resources to fix. It is important to catch and fix faults early in the development process to minimize these costs.

C. Decreases as we move the product towards live use: This option is incorrect. The cost of fixing faults decreases as we move further away from live use, not towards it. This is because the product is still in the development stage and changes can be made more easily and at a lower cost at this point.

D. Is more expensive if found in requirements than functional design: This option is partially correct. It is generally more expensive to fix faults that are found in the requirements stage than in the functional design stage. This is because fixing a fault in the requirements stage may require significant changes to the product, while fixing a fault in the functional design stage may only require minor adjustments.

E. Can never be determined: This option is incorrect. While it may be difficult to determine the exact cost of fixing a fault, it is possible to estimate it based on the resources and time required to make the necessary changes.

Therefore, the correct answer is:

The Answer is: B

Error guessing is best used

  1. As the first approach to deriving test cases

  2. After more formal techniques have been applied

  3. By inexperienced testers

  4. After the system has gone live

  5. Only by end users


Correct Option: B

Why is incremental integration preferred over “big bang” integration?

  1. Because incremental integration has better early defects screening and isolation ability

  2. Because “big bang” integration is suitable only for real time applications

  3. Incremental integration is preferred over “Big Bang Integration” only for “bottom up” development model

  4. Because incremental integration can compensate for weak and inadequate component testing


Correct Option: A

Why is it necessary to define a Test Strategy?

  1. As there are many different ways to test software, thought must be given to decide what will be the most effective way to test the project on hand.

  2. Starting testing without prior planning leads to chaotic and inefficient test project

  3. A strategy is needed to inform the project management how the test team will schedule the test-cycles

  4. Software failure may cause loss of money, time, business reputation, and in extreme cases injury and death. It is therefore critical to have a proper test strategy in place.


Correct Option: D

AI Explanation

To answer this question, you need to understand the purpose and importance of a Test Strategy.

Option A) As there are many different ways to test software, thought must be given to decide what will be the most effective way to test the project on hand. - This option is correct because a Test Strategy helps in determining the most effective and efficient way to test the software based on the project requirements and constraints. It considers factors such as the project scope, objectives, risks, resources, and timelines to determine the appropriate testing approach.

Option B) Starting testing without prior planning leads to a chaotic and inefficient test project - This option is correct because a Test Strategy provides a structured approach to testing by defining the scope, objectives, and test techniques to be used. It helps in avoiding ad-hoc testing and ensures that testing efforts are well-planned and organized.

Option C) A strategy is needed to inform the project management how the test team will schedule the test cycles - This option is correct because a Test Strategy includes the scheduling and sequencing of test activities, including test cycles. It helps in communicating the testing timelines and milestones to the project management and stakeholders.

Option D) Software failure may cause loss of money, time, business reputation, and in extreme cases injury and death. It is therefore critical to have a proper test strategy in place. - This option is correct because a Test Strategy is critical for ensuring the quality and reliability of the software being developed. It helps in identifying potential risks and mitigating them through effective testing. Software failures can have severe consequences, such as financial loss, damage to reputation, and even safety hazards. A proper test strategy helps in minimizing these risks and ensuring that the software meets the desired quality standards.

The correct answer is D. This option is correct because it emphasizes the critical importance of having a proper test strategy in place to prevent potential software failures and their associated consequences.

Which of the following statements about component testing is not true?

  1. Component testing should be performed by development

  2. Component testing is also know as isolation or module testing

  3. Component testing should have completion criteria planned

  4. Component testing does not involve regression testing


Correct Option: D
  1. As soon as the code is written

  2. During the design stage

  3. When the requirements have been formally documented

  4. As soon as possible in the development life cycle


Correct Option: D

Why is testing necessary?

  1. Because testing is good method to make there are not defects in the software

  2. Because verification and validation are not enough to get to know the quality of the software

  3. Because testing measures the quality of the software system and helps to increase the quality

  4. Because testing finds more defects than reviews and inspections.


Correct Option: C

What is difference between black box testing and white box testing?

  1. Black box testing is when we do not have knowledge of testing and in white box testing we have knowledge of testing.

  2. Black box testing is when we do not know the functionality and in white box testing we know the functionality.

  3. Black box testing is when we do not know code used and in white box testing we know the code used.

  4. Black box testing is when we test application randomly and in white box testing we test application using proper test strategy.


Correct Option: C

Functional system testing is

  1. Testing that the system functions with other systems

  2. Testing that the components that comprise the system function together

  3. Testing the end to end functionality of the system as a whole

  4. Testing the system performs functions within specified response times


Correct Option: B

The difference between re-testing and regression testing is

  1. Re-testing ensures the original fault has been removed; regression testing looks for unexpected side-effects

  2. Re-testing looks for unexpected side-effects; regression testing ensures the original fault has been removed

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

  4. Re-testing is done by developers; regression testing is done by independent testers


Correct Option: A

Testing should be stopped when

  1. All the planned tests have been run

  2. Time has run out

  3. All faults have been fixed correctly

  4. Both 1 and 3

  5. It depends on the risks for the system being tested


Correct Option: E

AI Explanation

To answer this question, we need to understand the concept of when to stop testing. Let's go through each option to understand why it is correct or incorrect:

Option A) All the planned tests have been run - This option is incorrect because stopping testing just because all the planned tests have been run does not guarantee that all potential risks and faults have been identified. There may still be undiscovered issues that need to be addressed.

Option B) Time has run out - This option is incorrect because stopping testing just because time has run out does not ensure that all necessary testing has been conducted. It is possible that important tests were not executed due to time constraints.

Option C) All faults have been fixed correctly - This option is incorrect because fixing all identified faults does not necessarily mean that all potential risks and issues have been addressed. There may still be undiscovered faults or risks that need to be evaluated.

Option D) Both 1 and 3 - This option is incorrect because as discussed above, stopping testing just because all planned tests have been run or all faults have been fixed correctly does not guarantee that all risks and issues have been considered.

Option E) It depends on the risks for the system being tested - This option is correct because the decision to stop testing should be based on the risks associated with the system being tested. Testing should continue until an acceptable level of risk has been achieved or until the stakeholders, such as the project manager or product owner, determine that the level of risk is acceptable.

The correct answer is E) It depends on the risks for the system being tested. This option is correct because stopping testing should be based on the level of risk associated with the system.

What is Parallel testing?

  1. Parallel testing is a type of testing where the tester reconciles the output of the new system to the output of the current system, in order to verify the new system operates correctly.

  2. Two people testing an application on same machine.

  3. Testing one functionality simultaneously on two different machine having same hardware configuration.

  4. Testing two different functionality simultaneously.


Correct Option: A

Which of the following list contains only non-functional tests?

  1. Interoperability (compatibility) testing, reliability testing, performance testing

  2. System testing, performance testing

  3. Load testing, stress testing, component testing, portability testing

  4. Testing various configurations, beta testing, load testing


Correct Option: C
Explanation:

To solve this question, the user needs to understand the difference between functional and non-functional testing. Functional tests evaluate the behavior of a system or component against the specifications, while non-functional tests evaluate the non-behavioral aspects of a system or component such as its performance, reliability, and usability.

Now, let's go through each option and determine which ones contain only non-functional tests:

A. Interoperability (compatibility) testing, reliability testing, performance testing: This option contains both functional and non-functional tests. Interoperability and compatibility testing is a type of functional testing, while reliability and performance testing are non-functional tests.

B. System testing, performance testing: This option contains both functional and non-functional tests. System testing is a type of functional testing, while performance testing is a non-functional test.

C. Load testing, stress testing, component testing, portability testing: This option contains only non-functional tests. Load testing and stress testing are non-functional tests that evaluate the performance of a system under different loads and stress levels. Component testing is a type of functional testing that evaluates the behavior of individual components, but portability testing is a non-functional test that evaluates the ability of a system to run on different hardware and software platforms.

D. Testing various configurations, beta testing, load testing: This option contains both functional and non-functional tests. Testing various configurations and beta testing are types of functional testing, while load testing is a non-functional test.

Therefore, the answer is: C. Load testing, stress testing, component testing, portability testing.

  1. Number of detected defects, testing cost

  2. Number of residual defects in the test object.

  3. Percentage of completed tasks in the preparation of test environment; test cases prepared

  4. Number of test cases run / not run; test cases passed / failed


Correct Option: D

Which of the following techniques are black box techniques?

  1. State transition testing, code testing, agile testing

  2. Equivalence partitioning, state transition testing, decision table testing

  3. System testing, acceptance testing, equivalence partitioning

  4. System integration testing, system testing, decision table testing


Correct Option: B
- Hide questions