SOFTWARE TESTING PART -1

February 20th, 2010 by

TESTING- it the process of identifying and detecting the defect in a product.

DEFECT- defect are variance from desired product not meeting the customer requirement expected result is not equal to actual result

Expected result-what be executing for the product.

Actual result –what the product actually gives you.

Software testing are two types:

MANNUAL TESTING- Tester with test the application if any defects are there it will be given to the developer. Developer fixes the defect and gives it to Tester. Tester will check the fix is correct or not. This process is 100% tester involved and this process is called manual testing.

AUTOMATION TESTING-. Test automation is a process of writing a computer program to do testing that would otherwise need to be done manually. Once tests have been automated, they can be run quickly. This is often the most cost effective method for software products that have a long maintenance life, because even minor patches over the lifetime of the application can cause features to break which were working at an earlier point in time.

Software Testing can also be stated as the process of validating and verifying that a software program/application/product:

  1. Meets the business and technical requirements that guided its design and development;
  2. Works as expected; and
  3. Can be implemented with the same characteristics.

Functional vs non-functional testing

Functional testing refers to tests that verify a specific action or function of the code. These are usually found in the code requirements documentation, although some development methodologies work from use cases or user stories. Functional tests tend to answer the question of “can the user do this” or “does this particular feature work”.

Non-functional testing refers to aspects of the software that may not be related to a specific function or user action, such as scalability or security.

Defects and failures

Not all software defects are caused by coding errors. One common source of expensive defects is caused by requirement gaps, e.g., unrecognized requirements, which result in errors of omission by the program designer. A common source of requirements gaps is non functional requirement such as testability,scalability,maintainability,usability,performance and security.

Error (mistake), which results in a defect (fault, bug) in the software source code. If this defect is executed, in certain situations the system will produce wrong results, causing a failure.

Compatibility

A common cause of software failure (real or perceived) is a lack of compatibility with other  application software ,operating systems (or operating system versions, old or new), or target environments that differ greatly from the original (such as a terminal or GUI application intended to be run on the desktop  now being required to become a Web Application, which must render in  Web browser ).

Static vs. dynamic testing

There are many approaches to software testing Reviews, walkthroughs or inspections  are considered as static testing, whereas actually executing programmed code with a given set of test cases is referred to as dynamic testing.

Software verification and validation

Software testing is used in association with verification and validation.

  • Verification: Have we built the software right? (i.e., does it match the specification).
  • Validation: Have we built the right software? (i.e., is this what the customer wants).

QUALITY- quality is defined as meeting the customer requirment for the first time and every time

Why quality is required:

  1. It gives defect free product.
  2. It gives user friendliness product.
  3. Reusability.
  4. Security
  5. Durability-long term performance of the product.
  6. It improves productivity and competiveness in any organization.

QUALITY ASSUARANCE- it is planned and systemetic set of activites necessary to provide adequate confidence that products and services will confirm to specified requirement and meet user needs.

QUALITY CONTROL- it is a product oriented after finishing the whole product tester will identify the defects so it is defect detection but it is not rectify the defect that time is going touswe quality assuarer i.e. developer.