Quality Assurance

Ensuring Quality Development

Our Quality Assurance process complies with ISO and CMM standards.

Achieving Quality Goals

The primary purpose of testing effort is to uncover the system limitations, rectify them and deliver zero defect solutions.

Criteria that will justify test suspension are:

  • Hardware/software is not available at the times indicated in the project schedule.
  • Source code contains one or more critical defects, which seriously prevents or limits testing progress.
  • Assigned test resources are not available when needed by the test team.

If testing is suspended, resumption will only occur when the problem(s) that caused the suspension has been resolved. When a critical defect is the cause of the suspension, the “FIX” is verified by the test department before testing is resumed.

Our Quality Strategy

The test strategy consists of series of different tests that will be exercisedduring the development process. If any defects are found which seriously impact the test progress, the QA manager may choose to suspend testing.

Tests at Nichetech

Standards Test:

Focuses on checking whether the system meets the standards defined in the QA Standards document.

Functional Test:

Focuses on the behavior of the system. Overall, the functional tests will test the integrated system and verify that it meets the requirements defined in the requirements document.

Security Test:

Determine how secure the system is. The tests will verify that unauthorized user access to data is prevented.

Contingency Test:

Determines whether fail-over procedures integrated in the system works properly.

Stress and Load Test:

Subjects the system to high volume of data. The system is stress tested using twice the number of expected users.

Recovery Test:

Forces the system to fail in various ways and verifies that the recovery is properly performed. It is vitally important that all data is recovered after a system failure & no corruption of data occurs.

Compatibility Test:

Verifies that the system is compatible with various versions of Windows operating system.

Deployment Test:

Verifies that the application can be deployed under different software & hardware configurations.

Beta Test:

Reports any defects which are found and subjects the system to test that could not be performed in our test environment.

User Acceptance Test:

Once the system is ready for implementation User Acceptance Testing is performed. The purpose of the test is to confirm that the system is developed according to the specified user requirements and is ready for operational use.

Testing Implementation – Constraints, Risks  & Assumptions

The test plan and test schedule are based on the requirements document. Any change to the requirement affects the test schedule and is carried out post approval. We ensure zero defect by

  • Effectiveness:Testing all solutions thoroughly as per the detailed document furnished in the requirement analysis.
  • Efficiency:Carrying out all the tests are per schedule.