FREE Manual Testing Batch Starts in Enroll Now | +91-8143353888 | +91-7780122379

info@onlineitvidhya.com
+918143353888 | +917780122379

FREE Manual Testing

  • Q1: What is manual testing?
    A: Manual testing is the process of manually testing software applications to identify defects, errors, or bugs. It involves executing test cases without the use of automation tools.
  • Q2: What is the difference between verification and validation?
    A: Verification focuses on whether the software is being developed correctly, adhering to specifications and requirements. Validation, on the other hand, focuses on whether the software meets the customer's expectations and needs.
  • Q3: Explain the software development life cycle (SDLC) and its phases.
    A: SDLC is a process followed to develop software. Its phases include requirements gathering, analysis, design, development, testing, deployment, and maintenance.
  • Q4: What are the different levels of testing?
    A: The different levels of testing include unit testing, integration testing, system testing, and acceptance testing.
  • Q5: What is the difference between functional testing and non-functional testing?
    A: Functional testing verifies the functional requirements of the software, while non-functional testing verifies aspects such as performance, reliability, usability, security, and scalability.
  • Q6: Describe the difference between smoke testing and sanity testing.
    A: Smoke testing is conducted to ensure that the critical functionalities of an application work fine before proceeding with further testing. Sanity testing is a cursory testing to verify that the major functionalities of the application are working as expected.
  • Q7: What is the purpose of test cases?
    A: Test cases are designed to validate the behavior of the software application and to ensure that it meets the specified requirements. They serve as a step-by-step guide for testers to execute tests.
  • Q8: Explain the concept of test plan and test strategy.
    A: A test plan outlines the testing approach, objectives, scope, resources, and schedule for a project. A test strategy defines the overall testing strategy, such as the test levels, types, and techniques to be used.
  • Q9: What is the difference between test scenarios and test cases?
    A: Test scenarios represent a set of test conditions or situations that need to be tested. Test cases, on the other hand, are detailed steps that need to be executed to validate the test scenario.
  • Q10: How do you prioritize test cases?
    A: Test cases can be prioritized based on factors such as business impact, risk, criticality, complexity, and frequency of use.
  • Q11: What is test coverage and why is it important?
    A: Test coverage refers to the degree to which the software has been tested. It helps assess the thoroughness of testing and ensures that critical areas of the software are adequately covered.
  • Q12: What is regression testing?
    A: Regression testing is performed to ensure that changes or modifications to the software do not introduce new defects or impact existing functionality.
  • Q13: Explain the concept of boundary value analysis.
    A: Boundary value analysis is a testing technique that focuses on testing the values at the boundaries of valid and invalid input ranges. It helps identify defects at the edges of the input domain.
  • Q14: What is equivalence partitioning?
    A: Equivalence partitioning is a testing technique that divides the input domain into equivalent classes, where each class represents a set of valid or invalid inputs. It helps reduce the number of test cases while maintaining adequate test coverage.
  • Q15: What is the defect life cycle?
    A: The defect life cycle refers to the stages through which a defect passes, from identification and logging to closure. The stages typically include open, assigned, fixed, retested, and closed.
  • Q16: What is the difference between priority and severity?
    A: Priority refers to the order in which defects should be fixed, based on their impact on the business. Severity, on the other hand, represents the impact of a defect on the application's functionality.
  • Q17: Explain the concept of test data and test data preparation.
    A: Test data is the input data that is used to execute test cases. Test data preparation involves identifying and creating the necessary data to perform tests.
  • Q18: What is exploratory testing?
    A: Exploratory testing is an informal and unscripted approach to testing where the tester explores the software application to find defects, without relying on predefined test cases.
  • Q19: What are the advantages and disadvantages of manual testing?
    A: Advantages of manual testing include the ability to perform ad-hoc testing, human intuition and creativity, and cost-effectiveness for small-scale projects. Disadvantages include human errors, time-consuming nature, and limited scope for automation.
  • Q20: Describe the V-model in software testing.
    A: The V-model is a software development and testing approach that emphasizes a parallel testing phase corresponding to each development phase. It consists of verification activities on one side and validation activities on the other, forming a V-shape.
  • Q21: What is the difference between positive and negative testing?
    A: Positive testing focuses on validating the expected behavior of the software with valid inputs. Negative testing, on the other hand, aims to test the software's ability to handle invalid or unexpected inputs.
  • Q22: Explain the concept of ad-hoc testing.
    A: Ad-hoc testing is an unplanned and unstructured testing approach where the tester randomly tests the application without any predefined test cases or documentation.
  • Q23: How do you ensure good test coverage?
    A: To ensure good test coverage, it is important to analyze requirements thoroughly, identify different test scenarios, prioritize tests based on risks, and use techniques such as equivalence partitioning and boundary value analysis.
  • Q24: What is a test case template and what information should it include?
    A: A test case template is a document that provides a standardized format for writing test cases. It typically includes fields such as test case ID, test case description, preconditions, test steps, expected results, and actual results.
  • Q25: Describe the concept of test execution and test log.
    A: Test execution involves executing the test cases as per the test plan and recording the actual results. The test log is a document that captures the details of test execution, including test case status, defects found, and any deviations from expected results.
  • Q26: What is the difference between alpha testing and beta testing?
    A: Alpha testing is conducted by the developers or testers within the organization, while beta testing involves testing by end-users in a real-world environment before the software is released to the public.
  • Q27: Explain the concept of usability testing.
    A: Usability testing is performed to evaluate the user-friendliness of the software. It focuses on testing aspects such as ease of use, user interface, navigation, and overall user experience.
  • Q28: What is a test harness
    A: A test harness is a set of tools, utilities, and test data that are used to execute test cases. It provides a framework for automating and managing the testing process.
  • Q29: Describe the concept of test environment and test data setup.
    A: The test environment is a setup that replicates the production environment where the software will be deployed. Test data setup involves preparing the necessary data to create a realistic testing environment.
  • Q30: What is the purpose of a traceability matrix?
    A: A traceability matrix is a document that establishes a traceable link between the requirements and the test cases. It helps ensure that all requirements are adequately covered by test cases and allows for easy tracking of requirements throughout the testing process.
  • Q31: Explain the concept of test estimation.
    A: Test estimation involves estimating the effort, resources, and time required to complete testing activities. It helps in planning and allocating resources effectively and provides a basis for project scheduling.
  • Q32: What is the difference between static testing and dynamic testing?
    A: Static testing is a type of testing that is performed without executing the software. It includes activities such as reviews, inspections, and walkthroughs. Dynamic testing, on the other hand, involves executing the software and validating its behavior against expected results.
  • Q33: Describe the concept of test deliverables.
    A: Test deliverables are the documents or artifacts that are produced during the testing process. They include test plans, test cases, test scripts, test reports, and defect reports.
  • Q34: What is a test script and how is it different from a test case?
    A: A test script is a set of instructions or commands that are used to execute a test case. It provides step-by-step guidance to the tester on how to perform the test. A test case, on the other hand, is a broader concept that includes the test script as well as the expected results.
  • Q35: Explain the concept of test closure and test summary report.
    A: Test closure refers to the activities performed to formally close the testing phase. It includes gathering test-related metrics, preparing a test summary report, archiving test artifacts, and conducting a retrospective. The test summary report provides an overview of the testing activities, results, and metrics achieved during the testing phase.
  • Q36: How do you handle test case dependencies?
    A: Test case dependencies can be handled by identifying and sequencing the test cases in such a way that the dependent test cases are executed in the correct order. Dependencies should be clearly documented and communicated to ensure proper execution.
  • Q37: What is a test oracle?
    A: A test oracle is a mechanism or source of truth that is used to determine the expected results of a test case. It could be the requirements document, design specifications, or any other reference material that defines the expected behavior of the software.
  • Q38: Describe the concept of test execution and defect tracking tools.
    A: Test execution tools are software tools used to execute test cases, capture actual results, and manage test execution. Defect tracking tools are used to log, track, and manage defects found during testing. These tools provide functionalities such as defect logging, assignment, tracking, and reporting.
  • Q39: What is the difference between a test plan and a test strategy?
    A: A test plan is a document that outlines the approach, objectives, scope, resources, and schedule for testing a specific project. A test strategy, on the other hand, is a document that defines the overall testing strategy for an organization or a product line. It includes guidelines, standards, and best practices to be followed during testing.
  • Q40: Explain the concept of test-driven development (TDD).
    A: Test-driven development is an iterative development approach where tests are written before the code. The code is then developed incrementally to pass the tests. It helps in ensuring code quality, better test coverage, and faster feedback loops.
  • Q41: What is the difference between positive and negative test cases?
    A: Positive test cases validate the expected behavior of the software with valid inputs. Negative test cases, on the other hand, aim to test the software's ability to handle invalid or unexpected inputs.
  • Q42: Describe the concept of test data management.
    A: Test data management involves managing the data used for testing purposes. It includes activities such as data generation, data masking, data anonymization, and data provisioning to create realistic and representative test scenarios.
  • Q43: What is the difference between test basis and test case?
    A: Test basis refers to the documents or artifacts that serve as the foundation for test case creation. It includes requirements documents, design specifications, use cases, and user stories. Test cases, on the other hand, are the specific steps or conditions that need to be executed to validate the test basis.
  • Q44: Explain the concept of test effort estimation techniques.
    A: Test effort estimation techniques involve estimating the effort required to complete testing activities. Techniques such as expert judgment, historical data analysis, function points analysis, and test point analysis can be used to estimate test effort.
  • Q45: What is the difference between test plan and test strategy?
    A: A test plan outlines the approach, objectives, scope, resources, and schedule for testing a specific project. A test strategy, on the other hand, is a document that defines the overall testing strategy for an organization or a product line. It includes guidelines, standards, and best practices to be followed during testing.
  • Q46: Explain the concept of equivalence partitioning.
    A: Equivalence partitioning is a testing technique that divides the input domain into equivalent classes, where each class represents a set of valid or invalid inputs. It helps reduce the number of test cases while maintaining adequate test coverage.
  • Q47: What is the purpose of test coverage analysis?
    A: Test coverage analysis is performed to assess the thoroughness of testing. It helps identify areas of the software that have not been tested and ensures that critical areas are adequately covered.
  • Q48: Describe the concept of a test environment.
    A: A test environment is a setup that replicates the production environment where the software will be deployed. It includes hardware, software, network configurations, databases, and other components necessary to perform testing.
  • Q49: What is the difference between a defect and an issue?
    A: A defect is a variance or deviation from the expected behavior of the software. An issue, on the other hand, is a broader term that can refer to any problem, concern, or topic related to the software or the project.
  • Q50: Explain the concept of test data and test data preparation.
    A: Test data is the input data that is used to execute test cases. Test data preparation involves identifying and creating the necessary data to perform tests.
  • Q51: What is exploratory testing?
    A: Exploratory testing is an informal and unscripted approach to testing where the tester explores the software application to find defects, without relying on predefined test cases.
  • Q52: What are the advantages and disadvantages of manual testing?
    A: Advantages of manual testing include the ability to perform ad-hoc testing, human intuition and creativity, and cost-effectiveness for small-scale projects. Disadvantages include human errors, time-consuming nature, and limited scope for automation.
  • Q53: Describe the V-model in software testing.
    A: The V-model is a software development and testing approach that emphasizes a parallel testing phase corresponding to each development phase. It consists of verification activities on one side and validation activities on the other, forming a V-shape.
  • Q54: What is the difference between positive and negative testing?
    A: Positive testing focuses on validating the expected behavior of the software with valid inputs. Negative testing, on the other hand, aims to test the software's ability to handle invalid or unexpected inputs.
  • Q55: Explain the concept of ad-hoc testing.
    A: Ad-hoc testing is an unplanned and unstructured testing approach where the tester randomly tests the application without any predefined test cases or documentation.
  • Q56: How do you ensure good test coverage?
    A: To ensure good test coverage, it is important to analyze requirements thoroughly, identify different test scenarios, prioritize tests based on risks, and use techniques such as equivalence partitioning and boundary value analysis.
  • Q57: What is a test case template and what information should it include?
    A: A test case template is a document that provides a standardized format for writing test cases. It typically includes fields such as test case ID, test case description, preconditions, test steps, expected results, and actual results.
  • Q58: Describe the concept of test execution and test log.
    A: Test execution involves executing the test cases as per the test plan and recording the actual results. The test log is a document that captures the details of test execution, including test case status, defects found, and any deviations from expected results.
  • Q59: What is the difference between alpha testing and beta testing?
    A: Alpha testing is conducted by the developers or testers within the organization, while beta testing involves testing by end-users in a real-world environment before the software is released to the public.
  • Q60: Explain the concept of usability testing.
    A: Usability testing is performed to evaluate the user-friendliness of the software. It focuses on testing aspects such as ease of use, user interface, navigation, and overall user experience.
  • Q61: What is a test harness?
    A: A test harness is a set of tools, utilities, and test data that are used to execute test cases. It provides a framework for automating and managing the testing process.
  • Q62: Describe the concept of test environment and test data setup.
    A: The test environment is a setup that replicates the production environment where the software will be deployed. Test data setup involves preparing the necessary data to create a realistic testing environment.
  • Q63: What is the purpose of a traceability matrix?
    A: A traceability matrix is a document that establishes a traceable link between the requirements and the test cases. It helps ensure that all requirements are adequately covered by test cases and allows for easy tracking of requirements throughout the testing process.
  • Q64: Explain the concept of test estimation.
    A: Test estimation involves estimating the effort, resources, and time required to complete testing activities. It helps in planning and allocating resources effectively and provides a basis for project scheduling.
  • Q65: What is the difference between static testing and dynamic testing?
    A: Static testing is a type of testing that is performed without executing the software. It includes activities such as reviews, inspections, and walkthroughs. Dynamic testing, on the other hand, involves executing the software and validating its behavior against expected results.
  • Q66: Describe the concept of test deliverables.
    A: Test deliverables are the documents or artifacts that are produced during the testing process. They include test plans, test cases, test scripts, test reports, and defect reports.
  • Q67: What is a test script and how is it different from a test case?
    A: A test script is a set of instructions or commands that are used to execute a test case. It provides step-by-step guidance to the tester on how to perform the test. A test case, on the other hand, is a broader concept that includes the test script as well as the expected results.
  • Q68: Explain the concept of test execution and defect tracking tools.
    A: Test execution tools are software tools used to execute test cases, capture actual results, and manage test execution. Defect tracking tools are used to log, track, and manage defects found during testing. These tools provide functionalities such as defect logging, assignment, tracking, and reporting.
  • Q69: What is the difference between a test plan and a test strategy?
    A: A test plan is a document that outlines the approach, objectives, scope, resources, and schedule for testing a specific project. A test strategy, on the other hand, is a document that defines the overall testing strategy for an organization or a product line. It includes guidelines, standards, and best practices to be followed during testing.
  • Q70: Explain the concept of test-driven development (TDD).
    A: Test-driven development is an iterative development approach where tests are written before the code. The code is then developed incrementally to pass the tests. It helps in ensuring code quality, better test coverage, and faster feedback loops.
  • Q71: What is the difference between positive and negative test cases?
    A: Positive test cases validate the expected behavior of the software with valid inputs. Negative test cases, on the other hand, aim to test the software's ability to handle invalid or unexpected inputs.
  • Q72: Describe the concept of test data management.
    A: Test data management involves managing the data used for testing purposes. It includes activities such as data generation, data masking, data anonymization, and data provisioning to create realistic and representative test scenarios.
  • Q73: What is the difference between test basis and test case?
    A: Test basis refers to the documents or artifacts that serve as the foundation for test case creation. It includes requirements documents, design specifications, use cases, and user stories. Test cases, on the other hand, are the specific steps or conditions that need to be executed to validate the test basis.
  • Q74: Explain the concept of test effort estimation techniques.
    A: Test effort estimation techniques involve estimating the effort required to complete testing activities. Techniques such as expert judgment, historical data analysis, function points analysis, and test point analysis can be used to estimate test effort.
  • Q75: What is the difference between test plan and test strategy?
    A: A test plan outlines the approach, objectives, scope, resources, and schedule for testing a specific project. A test strategy, on the other hand, is a document that defines the overall testing strategy for an organization or a product line. It includes guidelines, standards, and best practices to be followed during testing.
  • Q76: Explain the concept of equivalence partitioning.
    A: Equivalence partitioning is a testing technique that divides the input domain into equivalent classes, where each class represents a set of valid or invalid inputs. It helps reduce the number of test cases while maintaining adequate test coverage.
  • Q77: What is the purpose of test coverage analysis?
    A: Test coverage analysis is performed to assess the thoroughness of testing. It helps identify areas of the software that have not been tested and ensures that critical areas are adequately covered.
  • Q78: Describe the concept of a test environment.
    A: A test environment is a setup that replicates the production environment where the software will be deployed. It includes hardware, software, network configurations, databases, and other components necessary to perform testing.
  • Q79: What is the difference between a defect and an issue?
    A: A defect is a variance or deviation from the expected behavior of the software. An issue, on the other hand, is a broader term that can refer to any problem, concern, or topic related to the software or the project.
  • Q80: Explain the concept of test data and test data preparation.
    A: Test data is the input data that is used to execute test cases. Test data preparation involves identifying and creating the necessary data to perform tests.
  • Q81: What is exploratory testing?
    A: Exploratory testing is an informal and unscripted approach to testing where the tester explores the software application to find defects, without relying on predefined test cases.
  • Q82: What are the advantages and disadvantages of manual testing?
    A: Advantages of manual testing include the ability to perform ad-hoc testing, human intuition and creativity, and cost-effectiveness for small-scale projects. Disadvantages include human errors, time-consuming nature, and limited scope for automation.
  • Q83: Describe the V-model in software testing.
    A: The V-model is a software development and testing approach that emphasizes a parallel testing phase corresponding to each development phase. It consists of verification activities on one side and validation activities on the other, forming a V-shape.
  • Q84: What is the difference between positive and negative testing?
    A: Positive testing focuses on validating the expected behavior of the software with valid inputs. Negative testing, on the other hand, aims to test the software's ability to handle invalid or unexpected inputs.
  • Q85: Explain the concept of ad-hoc testing.
    A: Ad-hoc testing is an unplanned and unstructured testing approach where the tester randomly tests the application without any predefined test cases or documentation.
  • Q86: How do you ensure good test coverage?
    A: To ensure good test coverage, it is important to analyze requirements thoroughly, identify different test scenarios, prioritize tests based on risks, and use techniques such as equivalence partitioning and boundary value analysis.
  • Q87: What is a test case template and what information should it include?
    A: A test case template is a document that provides a standardized format for writing test cases. It typically includes fields such as test case ID, test case description, preconditions, test steps, expected results, and actual results.
  • Q88: Describe the concept of test execution and test log.
    A: Test execution involves executing the test cases as per the test plan and recording the actual results. The test log is a document that captures the details of test execution, including test case status, defects found, and any deviations from expected results.
  • Q89: What is the difference between alpha testing and beta testing?
    A: Alpha testing is conducted by the developers or testers within the organization, while beta testing involves testing by end-users in a real-world environment before the software is released to the public.
  • Q90: Explain the concept of usability testing.
    A: Usability testing is performed to evaluate the user-friendliness of the software. It focuses on testing aspects such as ease of use, user interface, navigation, and overall user experience.
  • Q91: What is a test harness?
    A: A test harness is a set of tools, utilities, and test data that are used to execute test cases. It provides a framework for automating and managing the testing process.
  • Q92: Describe the concept of test environment and test data setup.
    A: The test environment is a setup that replicates the production environment where the software will be deployed. Test data setup involves preparing the necessary data to create a realistic testing environment.
  • Q93: What is the purpose of a traceability matrix?
    A: A traceability matrix is a document that establishes a traceable link between the requirements and the test cases. It helps ensure that all requirements are adequately covered by test cases and allows for easy tracking of requirements throughout the testing process.
  • Q94: Explain the concept of test estimation.
    A: Test estimation involves estimating the effort, resources, and time required to complete testing activities. It helps in planning and allocating resources effectively and provides a basis for project scheduling.
  • Q95: What is the difference between static testing and dynamic testing?
    A: Static testing is a type of testing that is performed without executing the software. It includes activities such as reviews, inspections, and walkthroughs. Dynamic testing, on the other hand, involves executing the software and validating its behavior against expected results.
  • Q96: Describe the concept of test deliverables.
    A: Test deliverables are the documents or artifacts that are produced during the testing process. They include test plans, test cases, test scripts, test reports, and defect reports.
  • Q97: What is a test script and how is it different from a test case?
    A: A test script is a set of instructions or commands that are used to execute a test case. It provides step-by-step guidance to the tester on how to perform the test. A test case, on the other hand, is a broader concept that includes the test script as well as the expected results.
  • Q98: Explain the concept of test execution and defect tracking tools.
    A: Test execution tools are software tools used to execute test cases, capture actual results, and manage test execution. Defect tracking tools are used to log, track, and manage defects found during testing. These tools provide functionalities such as defect logging, assignment, tracking, and reporting.
  • Q99: What is the difference between a test plan and a test strategy?
    A: A test plan is a document that outlines the approach, objectives, scope, resources, and schedule for testing a specific project. A test strategy, on the other hand, is a document that defines the overall testing strategy for an organization or a product line. It includes guidelines, standards, and best practices to be followed during testing.
  • Q100: Explain the concept of test-driven development (TDD).
    A: Test-driven development is an iterative development approach where tests are written before the code. The code is then developed incrementally to pass the tests. It helps in ensuring code quality, better test coverage, and faster feedback loops

Address

Address: 4-42-200, Plot No. 200, Near United Church, Asbestos Hills Colony, Post, IDPL Colony, Balanagar, Hyderabad, Telangana 500037

+91-8143353888

info@onlineitvidhya.com

Courses

Terms of Use Refund Policy Privacy Policy

Copyright 2021 OnlineITVidhya. All Rights Reserved.