testing Online Quiz - 35
| Description: testing Online Quiz - 35 | |
| Number of Questions: 20 | |
| Created by: Aliensbrain Bot | |
| Tags: testing |
A formal product evaluation performed by a customer as a condition of purchase
-
Black Box Testing
-
Acceptance Testing
-
User Acceptance testing
-
Boundary Testing
Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration
-
Scalability Testing
-
Benchmark Testing
-
Mutation Testing
-
Black Box Testing
Testing done on the application where bugs are purposely added to it
-
Mutation Testing
-
Component Testing
-
Agile Testing
-
Ad Hoc Testing
AI Explanation
To answer this question, you need to understand different types of testing and their purposes.
Option A) Mutation Testing - This option is correct. Mutation testing is a type of testing where bugs or faults are intentionally added to the code to check the effectiveness of the test cases. The objective is to see if the test cases can identify the injected bugs and fail accordingly.
Option B) Component Testing - This option is incorrect. Component testing refers to testing individual components or modules of an application in isolation, without purposely adding bugs to it.
Option C) Agile Testing - This option is incorrect. Agile testing is a testing approach that focuses on iterative development and testing in an agile software development environment. It does not involve purposely adding bugs to the application.
Option D) Ad Hoc Testing - This option is incorrect. Ad hoc testing is a testing approach where testing is performed without any specific plan or documentation. It does not involve purposely adding bugs to the application.
The correct answer is A) Mutation Testing. This option is correct because it involves intentionally adding bugs to the application to assess the effectiveness of the test cases.
Performance testing focused on ensuring the application under test gracefully handles increase in work load
-
Boundary Testing
-
Smoke Testing
-
Scalability Testing
-
Functional Testing
IEEE 829 test plan documentation standard contains all of the following except:
-
test items
-
test deliverables
-
test tasks
-
test environment
-
test specification
AI Explanation
To answer this question, we need to understand the IEEE 829 test plan documentation standard. The IEEE 829 standard provides guidelines for creating a test plan document.
Let's go through each option to understand why it is correct or incorrect:
Option A) Test items - This option is correct. The IEEE 829 standard includes a section for specifying the test items, which are the components or features being tested.
Option B) Test deliverables - This option is correct. The IEEE 829 standard includes a section for specifying the test deliverables, which are the documents or artifacts produced during the testing process.
Option C) Test tasks - This option is correct. The IEEE 829 standard includes a section for specifying the test tasks, which are the activities or actions to be performed during testing.
Option D) Test environment - This option is correct. The IEEE 829 standard includes a section for specifying the test environment, which includes the hardware, software, and other resources required for testing.
Option E) Test specification - This option is incorrect. The IEEE 829 standard does not include a specific section for test specification. Test specification typically refers to the detailed documentation of test cases or test scenarios, which may be included in the test plan but is not explicitly mentioned in the IEEE 829 standard.
The correct answer is E. The IEEE 829 test plan documentation standard does not include a specific section for test specification.
Non-functional system testing includes:
-
testing to see where the system does not function properly
-
testing quality attributes of the system including performance and usability
-
testing a system feature using only the software required for that action
-
testing a system feature using only the software required for that function
-
testing for functions that should not exist
Which of the following is NOT part of configuration management:
-
status accounting of configuration items
-
auditing conformance to ISO9001
-
identification of test versions
-
record of changes to documentation over time
-
controlled library access
What is the purpose of test completion criteria in a test plan:
-
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
To solve this question, the user needs to understand the purpose of test completion criteria in a test plan.
Test completion criteria are used to determine when to stop testing. The criteria ensure that the testing process is complete and that all necessary tests have been executed.
Option A: This is incorrect because test completion criteria are not used to determine when a specific test has finished its execution.
Option B: This is incorrect because test completion criteria are not used to ensure that the test case specification is complete.
Option C: This is incorrect because test completion criteria are not used to set the criteria used in generating test inputs.
Option D: This is incorrect because test completion criteria are not used to determine when test planning is complete.
Option E: This is correct because test completion criteria are used to plan when to stop testing. Once the criteria have been met, testing can be concluded.
Therefore, the answer is: E.
When a new testing tool is purchased, it should be used first by:
-
A small team to establish the best way to use the tool
-
Everyone who may eventually have some use for the tool
-
The independent testing team
-
The managers to see what projects it should be used in
-
The vendor contractor to write the initial scripts
AI Explanation
To answer this question, let's go through each option to understand why it is correct or incorrect:
Option A) A small team to establish the best way to use the tool - This option is incorrect because it suggests that only a small team should use the tool initially to figure out the best way to use it. However, this approach may limit the understanding and exploration of the tool's capabilities, as it may not involve all potential users who may have different perspectives and needs.
Option B) Everyone who may eventually have some use for the tool - This option is the correct answer. When a new testing tool is purchased, it is best to involve everyone who may eventually have some use for the tool. This approach allows for a broader understanding of the tool's features and functionalities and ensures that all potential users can provide feedback and insights.
Option C) The independent testing team - This option is incorrect because it suggests that only the independent testing team should use the tool initially. While the independent testing team may have an important role to play in evaluating and utilizing the tool, it is beneficial to involve a wider range of users to ensure comprehensive testing and utilization.
Option D) The managers to see what projects it should be used in - This option is incorrect because it suggests that only the managers should use the tool initially to determine which projects it should be used in. However, involving all potential users can provide valuable insights on how the tool can be utilized across different projects and teams.
Option E) The vendor contractor to write the initial scripts - This option is incorrect because it suggests that only the vendor contractor should use the tool initially to write the initial scripts. While the vendor contractor may have knowledge and expertise in using the tool, it is important to involve all potential users to ensure a comprehensive understanding and utilization of the tool.
The correct answer is Option B) Everyone who may eventually have some use for the tool. This option is correct because it allows for a broader understanding of the tool's capabilities and ensures that all potential users can provide feedback and insights.
Which of the following is NOT a black box technique:
-
Equivalence partitioning
-
State transition testing
-
LCSAJ
-
Syntax testing
-
Boundary value analysis
-
Performed by customers at their own site
-
Performed by customers at their software developer’s site
-
Performed by an independent test team
-
Useful to test bespoke software
-
Performed as early as possible in the lifecycle
To answer this question, the user needs to know the definition and purpose of beta testing.
Beta testing is a type of software testing that involves allowing real users to test a product before it is released.
Now, let's go through each option and explain why it is right or wrong:
A. Performed by customers at their own site: This option is correct. Beta testing is often performed by customers at their own site, as they are the ones who will be using the software in the real world and can provide valuable feedback to the developers.
B. Performed by customers at their software developer’s site: This option is incorrect. While customers may be invited to the software developer's site for testing, beta testing is generally performed at the customer's own site.
C. Performed by an independent test team: This option is incorrect. Beta testing is usually performed by real users, not an independent test team.
D. Useful to test bespoke software: This option is correct. Beta testing can be useful for testing bespoke software, as it allows the developers to get feedback from real users before releasing the product.
E. Performed as early as possible in the lifecycle: This option is incorrect. Beta testing is usually performed after the software has gone through alpha testing and is close to release.
Therefore, the correct answer is: A. Performed by customers at their own site.
The main focus of acceptance testing is:
-
finding faults in the system
-
ensuring that the system is acceptable to all users
-
testing the system with other systems
-
testing for a business perspective
-
testing by an independent test team
To solve the question, the user needs to understand the concept of acceptance testing, which is a type of testing that evaluates whether or not a system meets its business requirements and is acceptable for delivery to the end-users.
Now, let's go through each option and explain why it is right or wrong:
A. finding faults in the system: This option is incorrect because the main focus of acceptance testing is not to find faults in the system. Although, acceptance testing may uncover faults, but the primary objective is to ensure that the system meets the business requirements and is acceptable for delivery.
B. ensuring that the system is acceptable to all users: This option is partially correct because the main focus of acceptance testing is to ensure that the system is acceptable to the end-users, but not necessarily to all users. Acceptance testing is done to ensure that the system meets the business requirements and is acceptable to the stakeholders who will be using it.
C. testing the system with other systems: This option is incorrect because acceptance testing is not focused on testing the system with other systems. Acceptance testing is done to ensure that the system meets the business requirements and is acceptable for delivery to the end-users.
D. testing for a business perspective: This option is correct. Acceptance testing is performed to verify that the system meets the business requirements and is acceptable to the stakeholders who will be using it. The testing team evaluates the system from a business perspective to ensure that it meets all the necessary criteria.
E. testing by an independent test team: This option is incorrect because although acceptance testing may be performed by an independent test team, this is not the main focus of acceptance testing.
The Answer is: D
Test managers should not:
-
report on deviations from the project plan
-
sign the system off for release
-
re-allocate resource to meet original plans
-
raise incidents on faults that they have found
-
provide information for risk analysis and quality improvement
Unreachable code would best be found using:
-
code reviews
-
code inspections
-
a coverage tool
-
a test management tool
-
a static analysis tool
A tool that supports traceability, recording of incidents or scheduling of tests is called:
-
a dynamic analysis tool
-
a test execution tool
-
a debugging tool
-
a test management tool
-
a configuration management tool
Testing is not done to Improve software accuracy
-
True
-
False
A standard for software testing terminology is IEEE 802.11
-
True
-
False
Regression testing always involves testing whether modifications have introduced adverse side effects
-
True
-
False
To check whether we are developing the right product according to the customer requirements are not.
-
Validation
-
Verification
-
Quality Assurance
-
Quality Control
The review and approved document (i.e. Test plan, System Requirement Specification’s) is called as
-
Delivery Document
-
Baseline Document
-
Checklist
-
None of the above