One Shot Revesion

Topic Wise Question Bank
All Topics
    • ☆
      1
      Software EngineeringTesting
      Explain the difference between Unit Testing and Integration Testing.
      Combined Bank, SO(IT-24), 26 | Senior Officer (IT)

      Difference between Unit Testing and Integration Testing

      Unit TestingIntegration Testing
      Tests individual Module, Function, or Class.Tests the interaction between two or more integrated Modules.
      Performed before Integration Testing.Performed after Unit Testing.
      Usually performed by Developers.Performed by Developers or QA Testers.
      Focuses on the correctness of a single unit.Focuses on data flow and communication between modules.
      Uses Stubs and Drivers when required.Uses integrated modules to detect interface-related defects.
      Easy to identify and fix defects.Detects interface, communication, and integration defects.

      Example

      Unit Testing: Testing the login validation function independently.

      Integration Testing: Testing whether the Login Module correctly communicates with the Database Module and User Authentication Module.


    • ☆
      2
      Software EngineeringTesting
      Black box and white box testing.
      Islami, QA(Engineer), 25 | Bank



    • ☆
      3
      Software EngineeringTesting
      Testing is an activity that is performed to verify correct behavior of a program. Testing should be conducted in all the stages of program development. Describe different types of tests conducted in the implementation stage.
      CB, O(IT), 20 | Officer (IT)

      During the Implementation Stage of the Software Development Life Cycle (SDLC), different types of testing are performed to verify that the software functions correctly and meets the specified requirements.

      1. Unit Testing

      Unit Testing is performed to test individual modules, functions, or classes independently. It is usually conducted by developers to ensure that each unit works correctly.

      2. Integration Testing

      Integration Testing verifies that multiple modules work together correctly after integration. It checks the interfaces and data flow between modules.

      3. System Testing

      System Testing evaluates the complete integrated software system to ensure that it meets all functional and non-functional requirements.

      4. Acceptance Testing

      Acceptance Testing is performed by customers or end users to verify that the software satisfies business requirements and is ready for deployment. It includes User Acceptance Testing (UAT).

      These testing types ensure that the software is reliable, error-free, and ready for deployment by identifying defects at different levels of the implementation stage.


    • ☆
      4
      Data Center & VirtualizationTesting
      Define test plan and Test case.
      Pubali, SQA, 23 |

      A Test Plan is a formal document that defines the testing strategy, objectives, scope, resources, schedule, and activities required to test a software application. It serves as a roadmap for the testing process and ensures that all testing activities are carried out systematically.

      Contents of a Test Plan

      • Testing objectives and scope.
      • Testing strategy and approach.
      • Resources and responsibilities.
      • Test schedule and milestones.
      • Entry and exit criteria.
      • Risks and assumptions.

      What is a Test Case?

      A Test Case is a document that describes a specific scenario to verify whether a particular feature or function of a software application works as expected. It contains the input data, execution steps, expected result, and actual result.

      Contents of a Test Case

      • Test Case ID.
      • Test Scenario or Description.
      • Preconditions.
      • Test Steps.
      • Input Data.
      • Expected Result.
      • Actual Result.
      • Pass/Fail Status.



    • ☆
      5
      Software EngineeringTesting
      Write difference between Verification and Validation.
      Pubali, SQA, 23 |

      Difference Between Verification and Validation

      VerificationValidation
      Verification checks whether the software is built according to the specified requirements.Validation checks whether the software meets the user's needs and expectations.
      It answers the question: "Are we building the product right?"It answers the question: "Are we building the right product?"
      Performed during the development phase.Performed after the software is developed or during testing.
      Does not require executing the software.Requires executing the software.
      Uses techniques such as Review, Inspection, and Walkthrough.Uses techniques such as Functional Testing, System Testing, and User Acceptance Testing (UAT).
      Focuses on finding defects in design and documents.Focuses on finding defects in the actual software product.
      It is a Static Testing process.It is a Dynamic Testing process.

      Example

      Verification: Reviewing the Software Design Document to ensure it follows the requirements.
      Validation: Running the software to verify that the login functionality works correctly for users.



    • ☆
      6
      Software EngineeringTesting
      Difference between White Box testing and Black Box testing.
      Pubali, SQA, 23 |



    • ☆
      7
      Software EngineeringTesting
      What is defect report? Define test harness?
      Pubali, SQA, 23 |

      A Defect Report (also called a Bug Report) is a document used to record and track defects found during software testing. It provides complete information about the defect so that developers can identify, fix, and verify the issue efficiently.

      Contents of a Defect Report

      • Defect ID.
      • Defect Summary or Title.
      • Description of the defect.
      • Steps to reproduce the defect.
      • Expected Result.
      • Actual Result.
      • Severity and Priority.
      • Status (Open, Fixed, Closed, etc.).
      • Reporter and Assigned Developer.

      Example

      If a user enters a valid username and password but cannot log in, the tester records the issue in a Defect Report with all necessary details.

      What is a Test Harness?

      Answer:

      A Test Harness is a collection of software, test data, Test Drivers, and Test Stubs used to execute and test a software component automatically. It provides an environment for running tests and comparing the actual results with the expected results.

      Components of a Test Harness

      • Test Driver.
      • Test Stub.
      • Test Data.
      • Test Scripts.
      • Result Comparison and Reporting Tools.

      Example

      During Unit Testing, a Test Harness uses a Test Driver to call a function and a Test Stub to simulate dependent modules, then compares the actual output with the expected output.



    • ☆
      8
      Software EngineeringTesting
      Describes different Cycle of STLC.
      Pubali, SQA, 23 |

      Software Testing Life Cycle (STLC) is a sequence of activities performed during the software testing process to ensure that the software meets the specified quality requirements. Each phase has specific objectives and deliverables.

      Phases of STLC

      1. Requirement Analysis
      The testing team analyzes the software requirements to identify testable requirements, testing scope, and possible risks.

      2. Test Planning
      A Test Plan is prepared, which defines the testing strategy, resources, schedule, tools, responsibilities, and estimated effort.

      3. Test Case Development
      Testers design Test Cases, prepare Test Data, and review them to ensure complete test coverage.

      4. Test Environment Setup
      The required hardware, software, network, database, and testing tools are configured to create the testing environment.

      5. Test Execution
      The prepared Test Cases are executed. The actual results are compared with the expected results, and any defects found are reported.

      6. Defect Reporting and Tracking
      Detected defects are recorded in a Defect Report, assigned to developers, fixed, and retested until they are resolved.

      7. Test Closure
      Testing activities are completed, test reports are prepared, lessons learned are documented, and the testing process is formally closed.



    • ☆
      9
      Software EngineeringTesting
      Define software testing level. show that unit, integration, system and user acceptance testing. How these are complemented of each other
      Sonali Bank, ADA, 26 | ADA

      Software Testing Level : Software Testing Levels are the different stages of testing used to verify and validate that software works correctly and meets requirements.

      Types of Testing Levels

      1. Unit Testing

      • Definition: Testing of the smallest individual unit (function/module) of a program.
      • Purpose: To check each part works correctly.
      • Performed by: Developer.

      2. Integration Testing

      • Definition: Testing of combined modules to verify interaction between them.
      • Purpose: To find interface/communication errors.

      3. System Testing

      • Definition: Testing of the complete system as a whole.
      • Purpose: To ensure system meets functional and non-functional requirements.

      4. User Acceptance Testing (UAT)

      • Definition: Final testing performed by end users.
      • Purpose: To confirm system meets business needs and is ready for deployment.

      How They Complement Each Other

      • Unit Testing: Ensures each component is correct.
      • Integration Testing: Ensures components work together.
      • System Testing: Ensures the whole system works properly.
      • UAT: Ensures system satisfies user requirements.
      • These levels work step-by-step from small parts to full system, ensuring complete quality assurance.

    • ☆
      10
      Software EngineeringTesting
      Verification and validation are two process areas at CMMI level 3. For both of these areas (a) provide a definition (b) a description of how you can fulfill these areas in your software testing activities.
      BB, AME, 23 | AME/ANE/AE

      (a) Definition

      Verification: Verification is the process of evaluating work products such as requirements, design, and code against predefined standards and specifications. It answers the question: “Are we building the product correctly?”

      Validation: Validation focuses on evaluating the final product to ensure it meets user needs and expectations. It answers the question: “Are we building the right product?”

      (b) Implementation of Verification and Validation in Software Testing

      Verification Activities

      Requirement Analysis: Functional and non-functional requirements are reviewed to identify testable requirements. A Requirement Traceability Matrix (RTM) is created to ensure each requirement is covered by test cases.

      Test Planning and Documentation: A test plan is prepared defining scope, objectives, tools, and schedules to verify alignment with requirements.

      Test Case Design and Development: Test cases are designed to verify individual components, including unit testing of modules.

      Test Environment Setup: The test environment is configured to simulate real conditions, and smoke testing is performed.

      Validation Activities

      System Testing: The complete system is tested to validate overall functionality.

      User Acceptance Testing (UAT): End users test the system to ensure it meets real-world requirements.

      Performance and Usability Testing: Confirms system performance and user experience.

      Test Execution and Bug Reporting: Test cases are executed, defects are logged, and fixes are retested.

      Test Closure and Reporting: Test results are analyzed and documented, and lessons learned are discussed.


Leave a Comment

WhatsApp Telegram Messenger