Technical Questions

Static Testing, a software testing technique in which the software is tested without executing the code. This Techniques provide a powerful way to improve the quality and productivity of software development by assisting engineers to recognize and fix their own defects early in the software development process.

It has two parts as listed below:

Review - Typically used to find and eliminate errors or ambiguities in documents such as requirements, design, test cases, etc.

Static analysis - The code written by developers are analysed (usually by tools) for structural defects that may lead to defects.

In this software is tested without executing the code by doing Review, Walk Through, Inspection or Analysis etc.

Hence, Error guessing is not a static software testing technique.

The logical arrangement of the nodes of different networks to communicate is called as topology.

Statement coverage is a white box test design technique which involves execution of all the executable statements in the source code at least once. It is used to calculate and measure the number of statements in the source code which can be executed given the requirements.

When a thread is created the threads does not require any new resources to execute the thread shares the resources like memory of the process to which they belong to. The benefit of code sharing is that it allows an application to have several different threads of activity all within the same address space. Whereas if a new process creation is very heavyweight because it always requires new address space to be created and even if they share the memory then the inter process communication is expensive when compared to the communication between the threads.

- Normal completion

- Time limit exceeded

- Memory unavailable

- Bounds violation

- Protection error

- Arithmetic error

- Time overrun

- I/O failure

- Invalid instruction

- Privileged instruction

- Data misuse

- Operator or OS intervention

- Parent termination.