testing Online Quiz - 16
| Description: testing Online Quiz - 16 | |
| Number of Questions: 20 | |
| Created by: Aliensbrain Bot | |
| Tags: testing |
Which of the following is a major task of test planning?
-
Determining the test approach.
-
Preparing test specifications.
-
Evaluating exit criteria and reporting.
-
Measuring and analyzing results.
To answer this question, the user needs to understand the basic concepts of software testing. Test planning is a crucial stage in software testing, where a comprehensive approach is developed to ensure that the software meets the requirements and is free from defects.
Now, let's go through each option and explain why it is right or wrong:
A. Determining the test approach: This option is correct. Determining the test approach is a major task in test planning. The test approach includes identifying the scope of testing, selecting the right test techniques, and developing a comprehensive test strategy that guides the testing process.
B. Preparing test specifications: This option is incorrect. Preparing test specifications is an important task in test execution, but it is not a major task in test planning. Test specifications are developed based on the test strategy and approach that is defined in the test plan.
C. Evaluating exit criteria and reporting: This option is incorrect. Evaluating exit criteria and reporting are critical tasks in test closure, where the results of the testing are analyzed to determine if the software is ready for release. It is not a major task in test planning.
D. Measuring and analyzing results: This option is incorrect. Measuring and analyzing results are tasks that are performed during the test execution and test closure stages. It is not a major task in test planning.
Therefore, the correct answer is:
The Answer is: A. Determining the test approach.
Fault Masking is ?
-
Error condition hiding another error condition
-
Creating a test case which does not reveal a fault
-
Masking a fault by developer
-
Masking a fault by a tester
AI Explanation
To answer this question, you need to understand the concept of fault masking.
Option A) Error condition hiding another error condition - This option is correct because fault masking refers to a situation where one error condition hides or masks another error condition. In other words, the presence of one fault in a system may prevent the detection of another fault.
Option B) Creating a test case which does not reveal a fault - This option is incorrect because fault masking is not related to creating test cases. It is about the presence of one error condition hiding another error condition.
Option C) Masking a fault by a developer - This option is incorrect because fault masking is not done intentionally by a developer. It is a situation that can occur unintentionally in a system when one fault hides another fault.
Option D) Masking a fault by a tester - This option is incorrect because fault masking is not done intentionally by a tester. It is a situation that can occur unintentionally in a system when one fault hides another fault.
The correct answer is A) Error condition hiding another error condition. This option is correct because it accurately describes the concept of fault masking.
A common test technique during component test is:
-
Usability testing
-
Security testing
-
Performance testing
-
Statement and branch testing
To answer this question, the user needs to be familiar with the different types of testing techniques used during software testing.
Option A: Usability testing is a type of testing that ensures the software is user-friendly and intuitive to use. This type of testing is usually performed during the user acceptance testing (UAT) phase of testing and is not used during the component testing phase. Therefore, option A is not the correct answer.
Option B: Security testing is a type of testing that ensures the software is secure and free from vulnerabilities. This type of testing is usually performed during the system testing phase and not used during the component testing phase. Therefore, option B is not the correct answer.
Option C: Performance testing is a type of testing that ensures the software's performance meets the expected requirements. This type of testing is usually performed during the system testing phase and not used during the component testing phase. Therefore, option C is not the correct answer.
Option D: Statement and branch testing is a type of testing that ensures each statement and branch of the code is executed at least once. This type of testing is performed during the component testing phase to ensure that the code is working as intended. Therefore, option D is the correct answer.
Therefore, the answer is: D. Statement and branch testing.
Which of the following is NOT true of test coverage criteria?
-
A measure of test coverage criteria is the percentage of user requirements covered.
-
Test coverage criteria can be measured in terms of items exercised by a test suite.
-
A measure of test coverage criteria is the percentage of faults found.
-
Test coverage criteria are often used when specifying test completion criteria.
AI Explanation
To answer this question, you need to understand test coverage criteria. Test coverage criteria refer to the extent to which a test suite or set of tests covers the requirements or components of a system. Let's go through each option to understand why it is correct or incorrect:
Option A) A measure of test coverage criteria is the percentage of user requirements covered. - This option is correct because one of the measures of test coverage criteria is indeed the percentage of user requirements covered. It helps determine how well the test suite covers the specified requirements.
Option B) Test coverage criteria can be measured in terms of items exercised by a test suite. - This option is incorrect because measuring test coverage criteria in terms of items exercised by a test suite is a valid approach. It helps assess the effectiveness of the tests in exercising the different components or functionalities of a system.
Option C) A measure of test coverage criteria is the percentage of faults found. - This option is correct because one of the measures of test coverage criteria is indeed the percentage of faults found. It helps evaluate how well the tests are able to detect faults or defects in the system.
Option D) Test coverage criteria are often used when specifying test completion criteria. - This option is correct because test coverage criteria are commonly used when determining test completion criteria. Test coverage criteria help define the minimum level of coverage that needs to be achieved before considering the testing phase complete.
The correct answer is Option B. This option is not true because test coverage criteria can indeed be measured in terms of items exercised by a test suite.
Therefore, the correct answer is B.
In prioritising what to test, the most important objective is to:
-
find as many faults as possible.
-
test high risk areas.
-
obtain good test coverage.
-
test whatever is easiest to test.
Given the following sets of test management terms (v-z), and activity descriptions (1-5), which one of the following best pairs the two sets? v ? test control w ? test monitoring x - test estimation y - incident management z - configuration control 1 - calculation of required test resources 2 - maintenance of record of test results 3 - re-allocation of resources when tests overrun 4 - report on deviation from test plan 5 - tracking of anomalous test results
-
v-3,w-2,x-1,y-5,z-4
-
v-2,w-5,x-1,y-4,z-3
-
v-3,w-4,x-1,y-5,z-2
-
v-2,w-1,x-4,y-3,z-5
The oracle assumption:
-
is that there is some existing system against which test output may be checked.
-
is that the tester can routinely identify the correct outcome of a test.
-
is that the tester knows everything about the software under test.
-
is that the tests are reviewed by experienced testers.
Which of the following is NOT a white box technique?
-
Statement testing
-
Path testing
-
Data flow testing
-
State transition testing
Some tools are geared more for developer use. For the 5 tools listed, which statement BEST details those for developers i)Performance testing tools ii)Coverage measurement tools iii)Test comparators iv)Dynamic analysis tools v)Incident management tools
-
i, iii. and iv. are more for developers
-
ii. and iv. are more for developers
-
ii, iii. and iv. are more for developers
-
ii. and iii. are more for developers
To answer this question, the user needs to know the purpose of each tool and who typically uses them.
i) Performance testing tools are primarily used by developers to evaluate the performance of their code or application under different conditions. These tools help developers identify and optimize performance bottlenecks.
ii) Coverage measurement tools are used to measure how much of the codebase is covered by automated tests. This information helps developers identify areas that need more testing and ensure that their code is thoroughly tested.
iii) Test comparators are tools that compare the expected output of a test to the actual output. These tools help developers identify errors in their code and ensure that the code is functioning as expected.
iv) Dynamic analysis tools are used to analyze running code and identify issues such as memory leaks, security vulnerabilities, and other runtime errors. These tools are often used by developers to improve the quality and security of their code.
v) Incident management tools are used to manage and track issues that arise in an application or software. While developers may use these tools to track issues related to their code, they are generally used by project managers, support teams, and other non-developer roles.
Based on the above information, we can conclude that:
A. i, iii. and iv. are more for developers - This is incorrect as option i is correct, but options iii and iv are not completely correct as test comparators and dynamic analysis tools are also used by testers and quality assurance teams.
B. ii. and iv. are more for developers - This is partially correct as coverage measurement tools and dynamic analysis tools are more commonly used by developers.
C. ii, iii. and iv. are more for developers - This is partially correct as coverage measurement tools, test comparators, and dynamic analysis tools are more commonly used by developers.
D. ii. and iii. are more for developers - This is partially correct as coverage measurement tools and test comparators are more commonly used by developers.
Therefore, the correct answer is:
The Answer is: B. ii. and iv. are more for developers.
Which of the following activities should be performed during the selection and implementation of a testing tool i) Investigate the organization's test process. ii) Conduct a proof of concept. iii) Implement the selected tool on a project behind schedule to save time. iv) Identify coaching and mentoring requirements for the use of the selected tool
-
i, ii, iii
-
ii, iii, iv
-
i, iii, iv
-
i, ii, iv
AI Explanation
To answer this question, you need to understand the activities involved in the selection and implementation of a testing tool. Let's go through each option to understand why it is correct or incorrect:
Option A) i, ii, iii - This option is incorrect because it includes activity iii, which suggests implementing the selected tool on a project behind schedule to save time. This is not a recommended practice as it can introduce additional risks and potentially worsen the situation.
Option B) ii, iii, iv - This option is incorrect because it does not include activity i, which is to investigate the organization's test process. Understanding the organization's test process is crucial in selecting and implementing a testing tool that aligns with the organization's needs and requirements.
Option C) i, iii, iv - This option is incorrect because it does not include activity ii, which is to conduct a proof of concept. Conducting a proof of concept helps evaluate the tool's capabilities and suitability before making a final decision.
Option D) i, ii, iv - This option is correct because it includes all the recommended activities during the selection and implementation of a testing tool.
The correct answer is D. This option is correct because it includes investigating the organization's test process (i), conducting a proof of concept (ii), and identifying coaching and mentoring requirements (iv), which are all important steps in ensuring the successful selection and implementation of a testing tool.
Which of the following benefits are MOST likely to be achieved by using test Tools i) Easy to access information about tests and testing. ii) Reduced maintenance of testware. iii) Easy and cheap to implement. iv) Greater consistency of tests.
-
ii and iv
-
ii and iii
-
i and iv
-
i and iii
AI Explanation
To answer this question, you need to understand the benefits of using test tools. Let's go through each option to understand why it is correct or incorrect:
Option A) ii and iv - This option is incorrect because it includes only two benefits, but the correct answer has four benefits.
Option B) ii and iii - This option is incorrect because it includes only two benefits, but the correct answer has four benefits.
Option C) i and iv - This option is correct because it includes the benefits of easy access to information about tests and testing (i) and greater consistency of tests (iv), both of which are likely to be achieved by using test tools.
Option D) i and iii - This option is incorrect because it includes the benefit of easy access to information about tests and testing (i), but it does not include the benefit of reduced maintenance of testware (ii), which is also likely to be achieved by using test tools.
The correct answer is C. This option is correct because it includes both the benefits of easy access to information about tests and testing and greater consistency of tests, which are likely to be achieved by using test tools.
With which of the following categories is a test comparator tool USUALLY Associated?
-
Tool support for performance and monitoring.
-
Tool support for static testing.
-
Tool support for test execution and logging.
-
Tool support for the management of testing and tests.
AI Explanation
To answer this question, you need to understand the different categories of tool support in software testing.
Option A) Tool support for performance and monitoring - This option is incorrect. Tools associated with performance and monitoring typically focus on measuring and analyzing the performance of the software during runtime, rather than comparing the actual results of a test with the expected results.
Option B) Tool support for static testing - This option is incorrect. Static testing tools are used to analyze the source code or documentation of the software without executing it. They do not involve comparing test results.
Option C) Tool support for test execution and logging - This option is correct. A test comparator tool is usually associated with test execution and logging. It is used to compare the actual results of a test with the expected results and log any discrepancies or failures.
Option D) Tool support for the management of testing and tests - This option is incorrect. Tools for the management of testing and tests typically focus on test planning, test case management, and test reporting. They do not specifically deal with comparing test results.
The correct answer is C) Tool support for test execution and logging. This option is correct because test comparator tools are commonly used in the execution phase of testing to compare actual and expected results and log any deviations or failures.
For which of the following would a static analysis tool be MOST useful?
-
Supporting reviews
-
Validating models of the software
-
Testing code executed in a special test harness
-
Enforcement of coding standards
To answer this question, the user needs to understand what a static analysis tool is and how it can be used in software development.
A static analysis tool is a software tool that examines the source code of a program without executing it. It checks for programming errors, security vulnerabilities, coding best practices, and other issues that can be detected without actually running the program.
Now let's go through each option and explain why it is right or wrong:
A. Supporting reviews: A static analysis tool can help identify potential issues in code before it goes to code review, but it is not the most useful tool for supporting reviews. Other tools, such as code review tools or collaboration platforms, would be more helpful in this scenario.
B. Validating models of the software: A static analysis tool may be useful in this scenario, but it is not the most useful tool. Model validation typically requires the use of specialized tools that can simulate system behavior and verify that the model accurately represents the software.
C. Testing code executed in a special test harness: A static analysis tool is not useful in this scenario because it does not execute the code. Instead, dynamic analysis tools would be more helpful as they can simulate the execution of code and test it in various scenarios.
D. Enforcement of coding standards: This option is the most appropriate answer. Static analysis tools are most useful in enforcing coding standards by identifying violations of coding standards, such as naming conventions, indentation, and other style guidelines. By using a static analysis tool, developers can ensure that their code adheres to the coding standards, which can improve the quality of the code and make it more maintainable.
Therefore, the correct answer is:
The Answer is: D
Find the mismatch
-
Test data preparation tools – Manipulate Data bases
-
Test design tools – Generate test inputs
-
Requirement management tools – Enables individual tests to be traceable
-
Configuration management tools – Check for consistence
Data flow analysis studies:
-
possible communications bottlenecks in a program.
-
the rate of change of data values as a program executes.
-
the use of data on paths through the code.
-
the intrinsic complexity of the code.
Static analysis tools are typically used by
-
Testers
-
Developers
-
Testers & Developers
-
None
What type of tools to be used for Regression Testing
-
Performance
-
Record/Playback
-
A. & B
-
None
The principal attributes of tools and automation are
-
Speed & efficiency
-
Accuracy & precision
-
All of the above
-
None of the above
Consider the following: Pick up and read the newspaper Look at what is on television If there is a program that you are interested in watching then switch the television on and watch the program Otherwise Continue reading the newspaper If there is a crossword in the newspaper then try and complete the crossword
-
SC = 1 and DC = 2
-
SC = 1 and DC = 3
-
SC = 2 and DC = 2
-
SC = 2 and DC = 3
Explanation: This scenario describes a simple decision-making process, where the person decides whether to watch TV or read the newspaper based on the availability of an interesting program and a crossword puzzle.
The steps in the process can be numbered as follows:
- Pick up and read the newspaper
- Look at what is on television
- If there is a program that you are interested in watching then switch the television on and watch the program
- Otherwise, continue reading the newspaper
- If there is a crossword in the newspaper then try and complete the crossword
The starting point is step 1, which is always executed. Then, depending on the situation, either step 3 or 4 is executed, but not both. Finally, step 5 is executed if there is a crossword puzzle in the newspaper.
Therefore, the structure chart for this scenario can be represented as follows:
+-----------+
| Start |
+-----------+
|
|
+-----------+
| Read news |
+-----------+
|
|
+-----------+
| Look TV |
+-----------+
/ \
/ \
+-----------+ +----------------+
| Watch | | Continue |
| program | | reading |
+-----------+ | newspaper |
+----------------+
|
|
+----------------+
| Try crossword |
+----------------+
As seen from the structure chart, there are two selection criteria (SC) and three decision criteria (DC).
The selection criteria are:
- SC1: Is there an interesting program on TV?
- SC2: If there is no interesting program on TV, continue reading the newspaper.
The decision criteria are:
- DC1: Watch the program.
- DC2: Continue reading the newspaper.
- DC3: Try to complete the crossword.
Therefore, the correct answer is D) SC = 2 and DC = 3.
Consider the following statements: i. An incident may be closed without being fixed. ii. Incidents may not be raised against documentation. iii. The final stage of incident tracking is fixing. iv. The incident record does not include information on test environments.
-
ii is true, i, iii and iv are false
-
i is true, ii, iii and iv are false
-
i and iv are true, ii and iii are false
-
i and ii are true, iii and iv are false
To answer this question, let's go through each statement:
i. An incident may be closed without being fixed. - This statement is true. In incident management, it is possible for an incident to be closed without being fixed if it is determined that the incident is not valid, a duplicate, or cannot be reproduced.
ii. Incidents may not be raised against documentation. - This statement is false. Incidents can be raised against documentation if there are errors, omissions, or inconsistencies in the documentation that impact the users.
iii. The final stage of incident tracking is fixing. - This statement is false. The final stage of incident tracking is not necessarily fixing. After an incident is reported, it goes through various stages such as triage, investigation, resolution, and closure. Fixing is just one of the stages in the process.
iv. The incident record does not include information on test environments. - This statement is false. The incident record may include information on test environments if it is relevant to the incident, such as if the incident occurred during testing or if it is specific to a particular test environment.
Based on the above analysis, we can conclude that statement i is true, and statements ii, iii, and iv are false.
Therefore, the correct answer is B.