Technical Questions

A test plan is the master document that contains all details pertaining to testing of the application. Its contents include:

Testing scope - what is included and what is not included in the testing of the current project 

Assumptions - what are the assumptions that are made for this project 

Milestones - major dates like when testing is going to begin, when it is planned to end, what is the trace review date, what is the production date etc. 

Resources - the resources working on this project along with their contact details 

Defect tracking mechanism - what defect tracking tool will be used, what is the SLA for fixing Critical to Low level IRs etc. 

Test management procedures - who will be notified when there is a critical IR, what reports will be sent daily, if status calls will be held daily or weekly, where will it be held, who is required to join etc. 

Work allocation - resource distribution if more projects are being tested 

Entry and exit criterion - when can a project be accepted for testing (eg. only when smoke testing passes) and when can a project be termed as testing complete (eg. when all testcases are executed and all high level bugs are fixed)

Distributed systems work in a network. They can share the network resources, communicate with each other.

Testing is a process used for revealing defects in s/w and for establishing that the s/w has attained a specific degree of quality.

The s/w testing group’s main objective is to ensure that the s/w is doing what it is supposed to do as well as the s/w is not doing what it is not supposed to do. With this objective, it is clear that it is necessary to have a separate group for testing the s/w other than the group which developed it.

Also, bugs in the s/w can cause severe monetary as well as other loss to the organization. So it is important to allocate some budget for the testing group.

1. Mutual exclusion (where at least one resource is non-sharable)

2. Hold and wait (where a process holds one resource and waits for other resource)

3. No preemption (where the resources can’t be preempted)

4. Circular wait (where p[i] is waiting for p[j] to release a resource. i= 1,2,…n

j=if (i!=n) then i+1

else 1 )

The Quality Factor is also defined, as Q. So it is a number, which reflects the lossness of a circuit. higher the Q, the lower are the losses.

the quality factor is measurement of efficiency (or effectiveness) of a device or circuitry. In literal sense quality factor means qualitative performance of a device.

Floating gate avalanche injection MOS (FAMOS) transistor is used in each cell of EPROM.

Interior gateways connect LANs of one organization, whereas exterior gateways connect the organization to the outside world.

It is the transfer of sufficient amount of the state of process from one machine to the target machine.