Software Testing Interview Questions Part 2
- What is Test Case?
Test cases are the set of positive and negative executable steps of a test scenario which has a set of pre-conditions, test data, expected result, post-conditions and actual results.
- What is Test Bed?
An environment configured for testing. Test bed consists of hardware, software, network configuration, an application under test, other related software.
- What is Test Environment?
Test Environment is the combination of hardware and software on which Test Team performs testing.
- Application Type: Web Application
- OS: Windows
- Web Server: IIS
- Web Page Design: Dot Net
- Server Side Scripting: ASP Dot Net
- Database: MS SQL Server
- Browser: IE/FireFox/Chrome
- What is Test Data?
Test data is the data that is used by the testers to run the test cases. Whilst running the test cases, testers need to enter some input data. To do so, testers prepare test data. It can be prepared manually and also by using tools.
For example, To test a basic login functionality having a user id, password fields. We need to enter some data in the user id and password fields. So we need to collect some test data.
- What is Test Harness?
A test harness is the collection of software and test data configured to test a program unit by running it under varying conditions which involves monitoring the output with expected output.
- What is Test Closure?
Test Closure is the note prepared before test team formally completes the testing process. This note contains the total no. of test cases, total no. of test cases executed, total no. of defects found, total no. of defects fixed, total no. of bugs not fixed, total no of bugs rejected etc.,
- What are the tasks of Test Closure activities in Software Testing?
Test Closure activities fall into four major groups.
Test Completion Check: To ensure all tests should be either run or deliberately skipped and all known defects should be either fixed, deferred for a future release or accepted as a permanent restriction.
Test Artifacts handover: Tests and test environments should be handed over to those responsible for maintenance testing. Known defects accepted or deferred should be documented and communicated to those who will use and support the use of the system.
Lessons learned: Analyzing lessons learned to determine changes needed for future releases and projects. In retrospective meetings, plans are established to ensure that good
practices can be repeated and poor practices are not repeated
Archiving results, logs, reports, and other documents and work products in the CMS (configuration management system).
- What is test coverage?
Test coverage helps in measuring the amount of testing performed by a set of tests.
Test coverage can be done on both functional and non-functional activities. It assists testers to create tests that cover areas which are missing.
- What is Code coverage?
Code coverage is different from Test coverage. Code coverage is about unit testing practices that must target all areas of the code at least once. It is usually done by developers or unit testers.
- List out Test Deliverables?
- Test Strategy
- Test Plan
- Effort Estimation Report
- Test Scenarios
- Test Cases/Scripts
- Test Data
- Requirement Traceability Matrix (RTM)
- Defect Report/Bug Report
- Test Execution Report
- Graphs and Metrics
- Test summary report
- Test incident report
- Test closure report
- Release Note
- Installation/configuration guide
- User guide
- Test status report
- Weekly status report (Project manager to client)
- What is Unit Testing?
Unit Testing is also called as Module Testing or Component Testing. It is done to check whether the individual unit or module of the source code is working properly. It is done by the developers in the developer’s environment.
- What is Integration Testing?
Integration Testing is the process of testing the interface between the two software units. Integration testing is done by three ways. Big Bang Approach, Top-Down Approach, Bottom-Up Approach
- What is System Testing?
Testing the fully integrated application to evaluate the system’s compliance with its specified requirements is called System Testing AKA End to End testing. Verifying the completed system to ensure that the application works as intended or not.
- What is Big Bang Approach?
Combining all the modules once and verifying the functionality after completion of individual module testing.
Top down and bottom up are carried out by using dummy modules known as Stubs and Drivers. These Stubs and Drivers are used to stand-in for missing components to simulate data communication between modules.
- What is Top-Down Approach?
Testing takes place from top to bottom. High-level modules are tested first and then low-level modules and finally integrating the low-level modules to a high level to ensure the system is working as intended. Stubs are used as a temporary module if a module is not ready for integration testing.
- What is Bottom-Up Approach?
It is a reciprocate of the Top-Down Approach. Testing takes place from bottom to up. Lowest level modules are tested first and then high-level modules and finally integrating the high-level modules to a low level to ensure the system is working as intended. Drivers are used as a temporary module for integration testing.
The future scope of Software testing is truly promising and the opportunities are endless.If you are someone who is interested in choosing Testing as a career, join the software testing training courses in kochi. Software testing course in Kochi gives you an opportunity to learn automation under industrial experts and live projects. Special attention is given to each student and they will get an exceptional learning experience. Specially designed modular courses enhance the testing skills and overall capability of the students.