What is Software Testing ?

The process of identifying the bugs/errors in the Project/Product (Software) is known as software testing. The test engineer will check whether the project/product/application is as per the client requirement or not ? Finally, we have ensured quality.

Testing is the process of identifying defects, where a defect is any variance/difference between actual results and expected results.

“In the application, a mistake/wrong in coding is called Error, error found by the tester is called Defect, defect accepted by development team then it is called Bug, build does not meet the requirements then it is Failure.”

What is Bug and Defect ?

Deviation from the requirement is nothing but Bug/Defect.

DEFECT:
It can be simply defined as a variance between the expected results and actual results. The defect is an error found after the build or application is released development team into the testing team. It commonly refers to several issues with the software project or products, with their external behavior
or with its internal features. In other words, a Defect is a difference between expected and actual results in the context of testing. It is the deviation of the customer requirement.

Wrong:
When the requirements are not implemented by in the right way. In this defect is a variance from the given specification. It is Wrong.

Missing:
In the project or product, a requirement of the customer that was not fulfilled or satisfied. This is a variance from the requirement, an indication that is as per the requirement was not implemented.

Error:
When the system produces an outcome, which is not the expected one or a consequence of a par-ticular action, an operation is known as an error.
Error leads to a defect and usually raises due to various reasons.

The Error is a human mistake. An Error appears not only due to the logical mistake in the code made by the developer. Anyone in the team can make mistakes during the different phases of soft-ware development. For instance,
• BA (business analyst) may misinterpret or misunderstand requirements.
• The customer may provide insufficient or incorrect information.
• The architect may cause a flaw in software design.
• People on the team can also make mistakes due to unclear or insufficient requirements, time pressure, lethargy, or other reasons.

Human errors may occur for many reasons such as:
o Stupidity:
o Negligence:
o Inexperience:
o Miscommunication:
o Misunderstanding:
o Complexity:
Bug:
Bug is the informal name of defects, which means that software or application is not working as per the requirement. In software testing, a software bug can also be issue, er-ror, fault, or failure.

Quality

Justification of all the requirements is nothing but quality.

Project

It will be developed based on client requirements. Once the development is done the client of team members will be using that particular project.
Example: Constructing Own House, ASTTrust, DeviGF

Product

It will be developed based on company requirements. Once it will be developed, the company will release it in the market based on the customer’s need the product will be chosen.
Example: Mobile, Car, Bike.

The Bidding/Request process for a project:

Whenever the company is a came to know that the client has the project then the company will submit the project/product estimations to the client.

1) Marketing BA

2) Engagement Manager.

 

Marketing BA is responsible to present the project estimation to the client.

 

Engagement Manager is responsible to maintain the Repo or Relation between the Client and Company. He acts as a bridge between Company and the Client.

SignOff / SigningOff:

The official agreement between the client and the company above the project is known as the signoff project.

Kick-Off Meeting:

Once the project is signed off, the high-level management will assemble for a meeting and select a project manager for the project.

The company will send official information (Mail) about the project to all the resources in the company.