Set Top box testing interview questions

A- Software testing is a process used to identify the correctness, completeness, and quality of developed computer software. In other words software testing is an activity to check whether the actual results match the expected results and to ensure that the software system is defect free.

Q) What is need software testing?

A- There are many reasons that we need software testing-

To check the reliability of the software.
To be ensured that the software does not contain any bug which can become a reason for failure.
To check the software was made according to its specification.
To check that the software meets its requirements.
To check that users are capable of using the software.
To check software works with other software and hardware it needs to work with

Q) What are the types of testing?

A-

1. Black Box Testing
2. White box Testing
3. Gray Box Testing

Q) What is White box testing?

A- White box testing is a process of testing in which we do code level testing. White box testing is performed based on the knowledge of how the system is implemented. White box testing includes analyzing data flow, control flow, information flow, coding practices, and exception and error handling within the system. White box testing requires access to the source code. Though white box testing can be performed any time in the life cycle after the code is developed, it is a good practice to perform white box testing during the unit testing phase.

Q) What is Black Box testing?

A- Black-box testing is a method of testing that examines the functionality of an application (e.g. what the software does) without knowing the internal structure of the application.

The types of testing under this strategy are totally based/focused on the testing for requirements and functionality of the work product/software application.

Q) What is Gray Box testing?

A- Gray Box Testing is a software testing method which is a combination of Black Box Testing method and White Box Testing method. In Black Box Testing, the internal structure of the item being tested is unknown to the tester and in White Box Testing the internal structure in known. In Gray Box Testing, the internal structure is partially known. This involves having access to internal data structures and algorithms for purposes of designing the test cases, but testing at the user, or black-box level.

Gray Box Testing is named so because the software program, in the eyes of the tester is like a gray/semi-transparent box; inside which one can partially see.
EXAMPLE

An example of Gray Box Testing would be when the codes for two units/modules are studied (White Box Testing method) for designing test cases and actual tests are conducted using the exposed interfaces (Black Box Testing method).

Q) What is Alpha testing?

A- Alpha testing is executed after completion of the formal test plan, but before the software is deployed in the market, and this can encompass white box as well as black box testing. The purpose of alpha testing is to measure the real users’ abilities to use and navigate the software application, and this is typically performed by internal employees and done in a lab environment so that user actions can be measured and analyzed.

Q) What is Beta testing?

A- Beta testing comes after alpha testing and primarily utilizes black box tactics. Beta testing is where real users outside the organization are solicited to play around with the software. This is normally the final “check and balance” system before the software is released en masse, although sometimes the beta version of a software application is released to the general public during this phase. This process helps identify and mitigate defects that were missed during the formal test plan, and helps configure the customer support resources and processes that will be needed post-launch.

Q) Who does white box testing?

A- White box testing is done by both Developer & tester. But tester should have coding knowledge. White box testing helps testers to find the location of bugs! When they look inside the code. Testers find the location of bugs, where the bug is & Developer debugs & fixes the bug .Finds why the bug has occurred. White box testing helps the tester to write test cases, remove unnecessary test cases, and add more required test cases which can cause the software to crash.

Q) What is unit testing?

A- The primary goal of unit testing is to take the smallest piece of testable software in the application, isolate it from the remainder of the code, and determine whether it behaves exactly as you expect. Each unit is tested separately before integrating them into modules to test the interfaces between modules. Unit testing has proven its value in that a large percentage of defects are identified during its use.

Unit Testing is a level of the software testing process where individual units/components of a software/system are tested. The purpose is to validate that each unit of the software performs as designed.

Q) Who does unit testing?

A- Unit tests should ideally be the Developer’s responsibility, since the tests are designed to validate methods/functionality as designed/desired by the developer. They would be short tests to validate that what he/she meant to do, is indeed what the code is doing.

In addition, changes to the code will be made by the developer in most cases, so it would be his /her responsibility to ensure that the unit tests are updated and reflect accurately the intended changes.

Q) Any unit testing tool?

A- Junit, Nunit, Aunit, TtestNG

Q) What is Agile testing?

A- Agile as the name refers implies something to do very quickly. Hence Agile Testing refers to validate the client requirements as soon as possible and make it customer friendly. As soon as the build is out, testing is expected to get started and report the bugs quickly if any found. As a Tester, you need to provide your thoughts on the client requirements rather than just being in the audience at the other end. Emphasis has to be laid down on the quality of the deliverable in spite of short time frame which will further help in reducing the cost of development and your feed backs will be implemented in the code which will avoid the defects coming from the end user.

Q) What is Sanity testing?

A- When there are some minor issues with software and a new build is obtained after fixing the issues then instead of doing complete regression testing a sanity is performed on that build. You can say that sanity testing is a subset of regression testing.

Sanity testing is done after thorough regression testing is over, it is done to make sure that any defect fixes or changes after regression testing does not break the core functionality of the product. It is done towards the end of the product release phase.

Sanity testing follows a narrow and deep approach with detailed testing of some limited features.

Sanity testing is like doing some specialized testing which is used to find problems in particular functionality.

Sanity testing is done with an intent to verify that end user requirements are met with not.

Sanity tests are mostly non scripted.

Q) What is Smoke testing?

A- In software testing, a smoke test is a collection of written tests that are performed on a system prior to being accepted for further testing. This is also known as a build verification test.