1.
Software Quality measures how well the software is designed, and how well it conforms to that design
Correct Answer
A. True
Explanation
Software quality is a measure of how well a software product is designed and how well it adheres to that design. This includes factors such as functionality, reliability, efficiency, maintainability, and usability. A high-quality software is one that meets the requirements and expectations of its users, performs its intended functions without errors, and is easy to use and maintain. Therefore, the statement "Software Quality measures how well the software is designed, and how well it conforms to that design" is true.
2.
Testing helps improve the quality of the product by ensuring that the product has which of the following? (Select all relevant options)
Correct Answer(s)
A. Product meets user requirements
B. Product meets performance standards
Explanation
Testing helps improve the quality of the product by ensuring that the product meets user requirements and performance standards. Testing is done to verify that the product functions as intended and satisfies the needs of the users. It also helps identify any performance issues or deviations from the desired standards. However, testing cannot guarantee that the product is 100% defect-free or that it has been exhaustively tested, as it is practically impossible to test every possible scenario and eliminate all defects.
3.
When to stop testing?
Correct Answer(s)
A. Critical and key test cases have been successfully completed.
B. Cost of testing does not justify the project cost
C. Defect detection rate falls below a certain specified level
Explanation
The correct answer suggests that testing should be stopped when critical and key test cases have been successfully completed. This means that the most important and essential tests have been conducted and passed, indicating that the system is functioning as expected. Additionally, if the cost of testing outweighs the potential benefits or value of the project, it may be more efficient to stop testing. Lastly, if the rate of defect detection falls below a certain specified level, it implies that the testing process is no longer effective in identifying and resolving issues, making further testing unnecessary.
4.
Agile testing is a mix of iterative and incremental approach.
Correct Answer
A. True
Explanation
Agile testing is a mix of iterative and incremental approach because it follows the principles of Agile methodology, which emphasizes continuous feedback and collaboration. In Agile testing, the testing process is divided into small iterations, where each iteration focuses on delivering a working software increment. This iterative approach allows for early and frequent testing, enabling quick feedback and faster identification of issues. Additionally, the incremental approach ensures that the software is developed and tested in small increments, allowing for continuous integration and delivery of valuable features to the end-users.
5.
Validation is reviews, walkthroughs and inspections
Correct Answer
B. False
Explanation
Validation is not reviews, walkthroughs, and inspections. Validation refers to the process of evaluating a system or component during or at the end of the development process to determine whether it satisfies the specified requirements. Reviews, walkthroughs, and inspections are part of the verification process, which involves evaluating a system or component to determine whether it meets specified requirements. Therefore, the correct answer is false.
6.
Identify all the functional testing types. (Select all relevant options)
Correct Answer(s)
A. Smoke testing
B. Sanity testing
C. Exploratory testing
Explanation
The correct answer includes smoke testing, sanity testing, and exploratory testing. These are all types of functional testing. Smoke testing is a preliminary test to check if the basic functionalities of the software are working properly. Sanity testing is performed to ensure that the major functionalities of the software are working as expected. Exploratory testing is a testing approach where the tester explores the software to find defects and gain knowledge about its functionalities. Compatibility testing, on the other hand, is not a type of functional testing but rather a type of non-functional testing that checks if the software works correctly on different platforms, browsers, or devices.
7.
Identify the advantages of Black Box testing from the list. (Select correct options)
Correct Answer(s)
A. Test is unbiased, as the developer and tester are independent of each other.
B. Test is done from the point of view of the user, and not the developer.
Explanation
Black box testing is a type of software testing where the internal workings of the system being tested are not known to the tester. The advantages of black box testing include the fact that it is unbiased, as the developer and tester are independent of each other. This means that the tester can provide an objective evaluation of the system without any preconceived notions or biases. Additionally, black box testing is done from the point of view of the user, not the developer. This ensures that the system is tested for its intended functionality and usability, making it more effective in identifying potential issues or bugs.
8.
Identify the disadvantages of whitebox testing.
Correct Answer(s)
A. A skilled tester is required to perform the testing, and this increases the cost.
B. It is impossible to look into every line of code, which could lead to problems and cause the application to fail.
Explanation
Whitebox testing, also known as clear box testing or structural testing, involves examining the internal structure and code of a software application. The given answer correctly identifies two disadvantages of whitebox testing. Firstly, it requires a skilled tester who possesses knowledge of the application's internal workings, which can increase the cost of testing. Secondly, it is impossible to inspect every line of code, leaving room for potential problems that may cause the application to fail. Additionally, the answer does not mention the third disadvantage mentioned in the question, which is that code optimization becomes a difficult task in whitebox testing.
9.
Test Scenario design is given more importance during Fresh Development testing
Correct Answer
A. True
Explanation
Test scenario design is given more importance during fresh development testing because it helps in identifying and defining the various scenarios that need to be tested. During fresh development testing, the focus is on testing the software or application from scratch, and test scenarios play a crucial role in ensuring comprehensive coverage of all possible scenarios. By designing effective test scenarios, testers can ensure that all functionalities and features of the software are thoroughly tested, leading to a higher quality product. Therefore, giving importance to test scenario design during fresh development testing is essential.
10.
The following are the various levels of testing: Identify the correct order:
1. System testing
2. Assembly testing
3. Unit testing
4. System Integration testing
5. User Acceptance testing
Correct Answer
A. 3,2,1,4,5
Explanation
The correct order of the various levels of testing is as follows:
1. Unit testing - This is the first level of testing where individual components or units of the software are tested independently.
2. Assembly testing - Once the units are tested, they are combined or assembled together and tested as a group to ensure that they function correctly when integrated.
3. System testing - After assembly testing, the entire system is tested to verify that it meets the specified requirements and functions as expected.
4. System Integration testing - This level of testing focuses on testing the interactions and interfaces between different systems or subsystems to ensure that they work together seamlessly.
5. User Acceptance testing - This is the final level of testing where the software is tested by end-users to determine whether it meets their requirements and is ready for deployment.
11.
What is correct about Unit testing? (select one)
Correct Answer
A. Lowest level of testing
Explanation
Unit testing is the lowest level of testing in software development. It involves testing individual units or components of code to ensure that they function correctly in isolation. This type of testing focuses on verifying the smallest units of code, such as functions or methods, and ensures that they work as expected. Unit testing can be performed using white box testing techniques, which involve examining the internal structure and implementation of the code. It is typically performed by the development team rather than the testing team.
12.
Component Integration testing is also called as API Testing.
Correct Answer
A. True
Explanation
Component Integration testing is also called API Testing because API testing focuses on testing the integration between different components or modules of an application. It involves testing the communication and interaction between these components to ensure that they work together correctly. API testing is specifically focused on testing the interfaces and interactions provided by APIs, which are used for integration between different software components. Therefore, it is correct to say that Component Integration testing is also called API Testing.
13.
Black box Testing is preffered to carry out System testing.
Correct Answer
A. True
Explanation
Black box testing is a type of testing where the tester does not have access to the internal workings or code of the system being tested. Instead, they focus on testing the system's functionality and behavior based on its inputs and outputs. This type of testing is preferred for system testing because it allows for a more comprehensive evaluation of the system's capabilities and ensures that it meets the specified requirements without considering the internal implementation details. Therefore, the given statement that black box testing is preferred for system testing is true.
14.
What is correct about UAT?
Correct Answer
A. Validates if the application is fit for deployement.
Explanation
UAT, or User Acceptance Testing, is a process that validates if the application is fit for deployment. This means that UAT ensures that the application meets the necessary requirements and functions properly before it is released to the end users. It is an important step in the software development lifecycle to ensure that the application is ready for actual use.
15.
Identify the correct type of KT. (select one)
Correct Answer
D. Incremental Approach
Explanation
The correct answer is Incremental Approach. Incremental approach is a software development method where the product is developed in multiple small increments or iterations. Each increment adds new functionality to the product, gradually building it up until it is complete. This approach allows for flexibility and adaptability, as changes can be made and feedback can be incorporated throughout the development process. It also allows for early delivery of a working product, which can be beneficial for clients and stakeholders.
16.
The objective of Transition Planning is to ensure the readiness of the project team and the client to begin the KT
Correct Answer
A. True
Explanation
Transition planning is an essential part of project management that focuses on preparing the project team and the client for the knowledge transfer (KT) phase. This involves ensuring that both parties are equipped with the necessary skills, resources, and knowledge to effectively transition from the project implementation phase to the KT phase. By ensuring readiness, the project team and the client can smoothly begin the KT process, leading to a successful project outcome. Therefore, the statement "The objective of Transition Planning is to ensure the readiness of the project team and the client to begin the KT" is true.
17.
Identify the correct components present in the KT plan. (Select all relevant options)
Correct Answer(s)
A. KT calendar
B. Milestones
C. Escalation Process
D. Training Process
Explanation
The correct components present in the KT plan are the KT calendar, milestones, escalation process, and training process. The KT calendar helps to schedule and organize knowledge transfer activities. Milestones are important checkpoints or goals that need to be achieved during the knowledge transfer process. The escalation process is necessary to address any issues or challenges that may arise during the transfer. Lastly, the training process ensures that the necessary training and knowledge transfer activities are conducted effectively.
18.
Knowledge is typically acquired by the Onsite team from the client SME's and is passed on to the offshore team on a daily basis.
Correct Answer
A. True
Explanation
The statement suggests that the knowledge is usually obtained by the onsite team from the client SMEs (Subject Matter Experts) and then shared with the offshore team on a daily basis. This implies that the onsite team plays a crucial role in gathering information from the client and transferring it to the offshore team. Therefore, the answer "True" indicates that the statement accurately reflects the typical process of knowledge acquisition and sharing between the onsite and offshore teams.
19.
Identify all the correct modes of Knowledge Transition. (select all the relevant options)
Correct Answer(s)
A. Conference Calls
B. Job shadowing of day to day activities
C. Self study
D. Query responses
Explanation
The correct modes of Knowledge Transition include conference calls, job shadowing of day to day activities, self study, and query responses. Conference calls allow for real-time communication and exchange of information between individuals or teams. Job shadowing provides a hands-on learning experience by observing and participating in daily tasks and activities. Self study involves independent learning and research to acquire new knowledge. Query responses involve addressing and answering questions to provide clarification and understanding.
20.
What are the different tools used for Requirement gathering process?
Correct Answer(s)
A. Prototypes
B. Use Cases
C. Data Flow diagrams
Explanation
The different tools used for the requirement gathering process include prototypes, use cases, and data flow diagrams. Prototypes help in visualizing and validating the requirements by creating a working model of the system. Use cases are used to identify and define the interactions between the system and its users, outlining various scenarios and actions. Data flow diagrams help in understanding and documenting the flow of data within a system, identifying inputs, outputs, and processes involved. These tools collectively aid in gathering and documenting requirements effectively.
21.
Functional requirements are classified as: (Select all the relevant options)
Correct Answer(s)
A. Business Requirements
C. Functional Specifications
D. User Requirements
Explanation
Functional requirements are classified into different categories based on their nature and purpose. Business requirements are the high-level objectives and goals that the software or system should achieve in order to meet the needs of the business. Functional specifications provide detailed descriptions of how the system should behave and what features it should have. User requirements define the specific needs and expectations of the end users regarding the functionality and usability of the system. Therefore, the given options of Business Requirements, Functional Specifications, and User Requirements are all relevant types of functional requirements.
22.
What is true about Constraints? (select all relevant options)
Correct Answer(s)
A. Constraints could be User constraints or system constraints.
C. Common area of constraints on the application are reliability, security, performance, usability, safety
Explanation
Constraints can be categorized as either user constraints or system constraints. Additionally, constraints are also referred to as quality factors. Common areas of constraints for an application include reliability, security, performance, usability, and safety.
23.
Requirements which are too subjective and have attributes that cannot be quantified are non testable.
Correct Answer
A. True
Explanation
Requirements that are too subjective and have attributes that cannot be quantified are considered non-testable. This means that it is difficult or impossible to create specific test cases or criteria to verify or validate these requirements. Since testing requires objective and measurable criteria, subjective and unquantifiable requirements cannot be effectively tested. Therefore, the statement is true.
24.
RTM establishes a relationship between two or more requirements.
Correct Answer
A. True
Explanation
RTM, or Requirements Traceability Matrix, is a tool used in project management to establish links between requirements and other project artifacts. It helps ensure that all requirements are met and that there is traceability throughout the project. By establishing a relationship between two or more requirements, RTM enables better understanding of dependencies and impacts between different project elements. Therefore, the given statement is true as RTM does indeed establish a relationship between requirements.
25.
What is determined during test strategizing phase of a project? (Select all relevant options)
Correct Answer(s)
A. Approach to be followed for testing
B. Different types of testing to be carried over in the project
C. Determination of Resource needs
D. Environments in which the application needs to be tested
Explanation
During the test strategizing phase of a project, the following are determined: the approach to be followed for testing, different types of testing to be carried out in the project, determination of resource needs, and the environments in which the application needs to be tested. These factors are crucial for planning and executing the testing activities effectively and efficiently.
26.
What are the major components of test strategy?
Correct Answer(s)
A. Objectives and critical success factors
B. Testing Approach
C. Test Milestones
D. Types and levels of testing
E. Test criteria
F. Test data Strategy
Explanation
The major components of a test strategy include objectives and critical success factors, testing approach, test milestones, types and levels of testing, test criteria, and test data strategy. These components are essential in defining the overall goals and objectives of the testing process, determining the approach and techniques to be used, setting milestones for progress tracking, identifying the different types and levels of testing required, establishing criteria for evaluating the success of the testing, and planning for the necessary test data. Option number 1 and 2 only does not cover all the major components of a test strategy.
27.
Risks - Identification, Mitigation and Contingency plan is a part of test strategy.
Correct Answer
A. True
Explanation
The statement is true because risks identification, mitigation, and contingency plan are essential components of a test strategy. In order to effectively plan and execute testing activities, it is important to identify potential risks that may impact the project, develop strategies to mitigate those risks, and create contingency plans to address any unforeseen issues that may arise during testing. By including these elements in the test strategy, the testing team can proactively manage risks and ensure the successful implementation of the testing process.
28.
What are the major components of a test plan? (select ONLY TWO options)
Correct Answer(s)
A. Testing Scope
B. Run plan creation
Explanation
A test plan is a document that outlines the objectives, approach, and scope of testing for a specific project. It includes various components such as testing scope, which defines the boundaries and limitations of testing activities, and run plan creation, which involves creating a detailed plan for executing the tests. These two components are crucial in ensuring that the testing process is well-defined and organized, allowing for effective and efficient testing of the project. The other options, escalation process and description of test designing, are not major components of a test plan and are therefore not the correct answers.
29.
For small projects or regular release based projects, the test plan and strategy could be documented together.
Correct Answer
A. True
Explanation
For small projects or regular release based projects, it is common practice to document the test plan and strategy together. This is because these types of projects usually have shorter timelines and fewer complexities compared to larger projects. Combining the test plan and strategy documentation helps in streamlining the testing process and ensures that all necessary information is easily accessible for the testing team. However, for larger and more complex projects, it is generally recommended to have separate documents for the test plan and strategy to provide more detailed and comprehensive information.
30.
Separate strategy documents are also prepared for automation or for other types of testing like performance.
Correct Answer
A. True
Explanation
Separate strategy documents are indeed prepared for automation or other types of testing like performance. This is because each type of testing requires its own specific approach, tools, and techniques. Having separate strategy documents helps in clearly defining the objectives, scope, and methodologies for each type of testing, ensuring that the testing efforts are focused and effective. It also helps in better planning, resource allocation, and tracking of progress for each type of testing. Therefore, the statement "Separate strategy documents are also prepared for automation or for other types of testing like performance" is true.