main()

{

float me = 1.1;

double you = 1.1;

if(me==you)

printf("yes");

else

printf("No");

}

a.) Testing and Debugging 

Testing is process of verifying if the application matches requirements and reporting bugs; Testing is usually done by an independent testing team while debugging is a process of finding and fixing bugs with the intention of reducing bugs; Debugging is usually done by the programmer.

b.) Two tier and Three tier architecture

In a two tier architecture there is a data server and a client application. Client application directly accesses the server data. In a three tier architecture there is a data server, a client application and a server application. Client application calls the server application which in turn fetches data from the data server and returns back to client application.

c.) Alpha testing and Beta testing

Alpha testing is conducting acceptance testing in the environment where the application was developed. It is done by the customer. Beta testing is conducting acceptance testing is the customer environment. It is done by the group of customers or users who will actually be using it.

d.) Static testing and dynamic testing

Static testing is checking the application without actually running the application whereas dynamic testing checks the application by running it.

a.) Quality Assurance

Quality assurance is an activity that establishes and evaluates the processes that produce products. Quality assurance would measure processes to identify weaknesses and then correct them to continually improve the process: Eg. Code review.

b.) Quality Control

Quality control is a process in which the product's quality is compared with standards and corrective actions taken if required. Quality control activities focus on identifying defects in the actual products produced. Eg. Testing.

c.) Test Case

A test case is a unit level document describing the inputs, steps of execution and the expected result of each test condition for every requirement from the BRD. Testers determine whether the application is working correctly or not based on the test case that is being executed. A test case is marked as "Pass" if the application works as expected and is marked as "Fail" if otherwise. Test cases also aide in generating test status metrics.

d.) Test Condition

Test condition is the condition on which the test execution evaluates to pass or fail. Eg of a test condition: Set Password field should accept a mix of Alphanumeric and Special characters on mandatory basis and throw error message otherwise.

e.) Test Script

Test script is the set of instructions performed on the application to verify its functions.

f.) Test Data

Test data is the input data used to test a particular functionality. Eg: Username and password to test a login screen.

g.) Test Bed

Test bed is the environment on which the testing is done and includes the software and hardware set up that is required for testing the application.

Software testing is verifying if a software meets the customer's requirements; if it has high quality; if it is bug free and if it is fit for use. Testing is important because it ensures that the product delivered is defect free which in turn emphasizes higher quality and proves to be cost effective.

Quality Assurance Manager (QA Manager) defines the process to be followed at each phase of SDLC. He defines the standards to be followed, the documents to be maintained and sets the standard for the product.

Where as it is the Project Manager’s responsibility to ensure that the things defined by QA manager are being implemented. He develops the product from start to finish with his team and ensures that the product which is to be rolled out is Defect free and it reaches the standards and views defined by QA Manager.

QA managers can audit the process for certain time periods which are being handled by the Project Manager.

Risk analysis is a method to determine how much risk is involved in something. In testing, it can be used to determine when to test something or whether to test something at all. Items with higher risk values should be tested early and often. Items with lower risk value can be tested later, or not at all. It can also be used with defects. Severity tells us how bad a defect is: "how much damage can it cause?" Priority tells us how soon it is desired to fix the defect: "should we fix this and if so, by when?"

Defects with High Severity and Priority are tested first.

While a test plan is being created, risks involved in testing the product are to be taken into consideration along with possibility of their occurrence and the damage they may cause along with solutions; if any. Detailed study of this is called as Risk Analysis.

Some of the risks could be:

New Hardware 

New Technology 

New Automation Tool 

Sequence of code delivery 

Availability of application test resources 

Identify and describe the risk magnitude indicators: High, Medium and Low

High magnitude means the effect of the risk would be very high and non-tolerable. Company may face severe loss and its reputation is at risk. Must be tested.

Medium: tolerable but not desirable. Company may suffer financially but there is limited liability or loss of reputation. Should be tested.

Low: tolerable. Little or no external exposure. Little or no financial loss. Company’s reputation unaffected. Might be tested.

Three perspectives of Risk Assessment: Effect, Cause and Likelihood.

To assess risk by Effect, identify a condition, event or action and try to determine its impact.

To asses risk by Cause is opposite of by Effect. Begin by stating an undesirable event or condition and identify the set of events that could have permitted the condition to exist.

To asses risk by Likelihood is to determine the probability that a requirement will not be satisfied.

Capability Maturity Model (CMM) is a model of 5 levels of process 'maturity' that determine effectiveness in delivering quality software. The 5 levels of CMM are described as below:

Level 1: Initial: - characterized by chaos, periodic panics, and heroic efforts required by individuals to successfully complete projects. Very few or none of the processes are in place.

Level 2: Repeatable: - Software Project Tracking, Requirements Management, Realistic Planning and Configuration Management Processes are in place; successful practices can be repeated.

Level 3: Defined: - Standard Software Development and Maintenance Processes are integrated throughout an organization. A Software Engineering Process Group is in place to oversee software processes, and training programs are used to ensure understanding and compliance.

Level 4: Managed: - Metrics are used to track productivity, processes, and products. Project performance is predictable, and quality is consistently high.

Level 5: Optimizing: - The focus is on continuous process improvement. The impact of new processes and technologies can be predicted and effectively implemented when required.

Any organization can start from any level, but its motto is to reach level 5; where the focus is continuous process improvement. By doing this, high quality s/w delivery is assured.

From this, we can see that the whole essence of CMM or CMMI is to produce quality software. It targets the whole organizational practices (or processes), which are believed to be the best across industries. Testing is part of Quality Assurance. CMM levels play an important role in an organization’s Quality Assurance effort. Thus testing plays an important role in determining CMM level.

A bug leakage results when a bug is detected which should have been detected in earlier builds/versions of the application.

A defect which exists during testing yet unfound by the tester which is eventually found by the tester/end-user is also called bug leakage.

A bug release is when a particular version of s/w is released with a set of known bug(s)/defect(s). These bugs are usually low severity and/or low priority bugs. It is done when the company can afford the existence of bug in the released s/w rather than the time/cost for fixing it in that particular version. These bugs are usually mentioned in the Release Notes.