Quality Assurance Software Testing

Quality Assurance Software Testing is an integral and critical phase of every software development project. And thus our developers and testers takes special care to ensure that the newly developed products or product enhancements meet all the functional and performance requirements and that those products are reliable and able to operate consistently under peak loads.

It is most effective to start testing early in the development cycle and to test iteratively, with every build. With this approach, defects are removed as the features are implemented. And as a result the product is ready for release much earlier.

The Testing process focuses primarily on evaluating or assessing product quality, which is realized through the following core practices:

• Find and document defects in software quality.
• Advise on the perceived software quality.
• Validate and prove the assumptions made in design and requirement specifications through concrete demonstration.
• Validate that the software product works as designed.
• Validate that the requirements are implemented appropriately.

Testing is applied to different types of targets, in different stages or levels of work effort. Testing is usually done at two levels:

Developer Testing

Developer testing denotes the test design and implementation most appropriately performed by the team of developers. The developers create their tests in such away so as to make them available to independent testing groups for execution.

Independent Testing

Independent testing denotes the test design and implementation most appropriately performed by someone who is independent from the team of developers.

The other levels include:

• Independent Stakeholder Testing - testing that is based on the needs and concerns of various stakeholders.
• Unit testing - testing that focuses on verifying the smallest testable elements of the software.
• Integration testing – testing to ensure that the components in the implementation model operate properly when combined to execute a use case.
• System Testing – testing to ensure that the system's end- to-end functioning elements operate properly.
• Acceptance Testing – testing to verify that the software is ready, and that it can be used by end users to perform those functions and tasks for which the software was built.