Quality Assurance Testing

Quality Assurance Testing /QC tests are very important to ensuring continued quality and repeatability of products and assemblies are maintained. This Quality Assurance Testing is essential in verifying that a product delivered to your customer will function properly and meet your design intent. Types of Quality Assurance Testing:

Acceptance of Quality Assurance Testing: Quality Assurance Testing the system with the intent of confirming readiness of the product and customer acceptance.

Ad Hoc (or Smoke) Quality Assurance Testing: Quality Assurance Testing without, or outside of a test plan. With some projects this type of Quality Assurance Testing is carried out as an adjunct to formal Quality Assurance Testing. If carried out by a skilled tester it can often find problems that are not caught in regular Quality Assurance Testing. Sometimes, if Quality Assurance Testing occurs very late in the development cycle, this will be the only kind of Quality Assurance Testing that can be performed.

Alpha Quality Assurance Testing: Quality Assurance Testing after code is mostly complete or contains most of the functionality and prior to users being involved. Sometimes a select group of users are involved. More often this Quality Assurance Testing will be performed in-house or by an outside Quality Assurance Testing firm in close cooperation with the Software Engineering.

Beta Quality Assurance Testing: Quality Assurance Testing after the product is code complete. Beta versions are often widely distributed among clients to ensure new features meet client expectations.

Compatibility Quality Assurance Testing: Quality Assurance Testing used to determine whether other system software components such as browsers, utilities, and competing software will conflict with the software being tested.

Configuration Quality Assurance Testing: Quality Assurance Testing to determine how well the product works with a broad range of hardware/peripheral equipment configurations as well as on different operating systems and software.

Functional Quality Assurance Testing: Quality Assurance Testing two or more modules together with the intent of finding defects, demonstrating that defects are not present, verifying that the module performs its intended functions as stated in the specification and establishing confidence that a program does what it is supposed to do.

Installation Quality Assurance Testing: Quality Assurance Testing with the intent of determining if the product will install a variety of platforms and how easily it installs.

Performance Quality Assurance Testing: Quality Assurance Testing with the intent of determining how quickly a product handles a variety of events.

Regression Quality Assurance Testing: Quality Assurance Testing with the intent to determine if bug fixes have been successful and have not created any new problems. Also requiring a set of tests to ensure no degradation of baseline functionality has occurred.

Security Quality Assurance Testing: This is especially important for database and network software in order to keep company data secure from mistaken, accidental or unauthorized users, as well as hackers.