●

What type of the issue is this?

• Electrical, protocol or interoperability
• Clarify whether an issue is due to a margin-related random problem or a consistently occurring problem

●

Issue severity

• Classify as hardware or software related

●

The name of test item is not easy to understand.

●

The R&D team may be familiar with the SPEC, but not with the CTS (Compliance Test Specification).

●

Understanding the test concept helps clarify the issue and make it more specific.

●

Testing environment requirements

●

Providing a controlled testing environment and equipment ensures that products are tested with precision and consistency

●

Right configuration & setup with premium equipment and experience

●

Parameters

●

Check Point

●

Expected Results

●

Compare with another sample to determine if it’s a single-sample issue.

●

Compare with previous models that have already passed/certified.

●

On-line, face-to-face, or inter-discuss with our experienced engineers who already execute hundreds/thousands of the same tests.

●

Conducting additional experiments (using additional tools/methods) to isolate or narrow down the possible causes of problem.

●

Applying a fix-try in a timing manner and providing instant verification results timely.

●

If there is a “known-fix” fit the problem exactly, we will definitely share it with your developer.

●

1st : Regression testing based on the issues.

●

2nd : Regression testing based on specific field, such as electrical, protocol or test groups.

●

3rd : Full run regression.

●

Provide the reference models for comparison

●

Help clients to understand the issue distribution (e.g. Electrical, Protocol, IOP...)

●

Identify general problem types or frequent issues

●

Analyze the frequent issues by brands, OEMs or product types

●

Distribution trend analysis