CUBRID Perl 8.4.1 QA Test Report

Product QA done by

Cubrid QA Team

QA participants

Zou Jing, Guo Rui

QA test duration

2012.03.20~ 2012.03.20

1. Quality Measurement Result

Functional Test

Performance Test

Security Test

※ Describe test results as Pass, Fail, Not Executed, or N/A (N/A means not applicable to the project; and tests planned but not executed are classified into the Not Executed category)

Pass

Pass

N/A

Quality indicator at realization phase

QA start conditions

CUBRID-PHP-8.4.1

Remark

Functional realization rate (%)

100%

100%

1. php_cubrid.c code's lines are 2731
2. Dev didn't provide code Complexity figures in hudson

# of source-code lines (LOC)

-

527

Unit test code coverage (%)

70%

76%

# of critical errors at the static analysis

0.00%

N/A

Code complexity

c10 or higher (%)

100%

N/A

c30 or higher (%)

0.50%

N/A

Coding standard conformance rate

N/A

N/A

Quality indicator at QA test phase

Quality objective

QA test result

Test case execution rate

100%

100%

Test success rate

100%

95%

7 failed cases were caused by cci problem

QA test code coverage

70%

76%

Error correction completion rate

100%

100%

No. of residual errors by criticality

Blocker

0

0

Critical

0

0

Major

0

0

Minor

0

0

Trivial

0

0

Security vulnerability by risk rating (#)

Critical

N/A

N/A

Major

N/A

N/A

Minor

N/A

N/A

Defect occurrence rate (All defects/KLOC)

N/A

N/A

Residual defect rate (# of not-fixed defects/KLOC)

N/A

N/A

Specifics of QA test defects

QA Test Result

Remark

Overall information (Effective defect)

Total

35

Active

9

Closed

26

Detailed information of closed defects (#)

Fixed

18

7 failed cases were caused by cci problem

Won't Fix

3

Cannot reproduce

0

PostPoned

9

Roll back

0

PostPone

0

By design

0

Not a Defect

Duplicate

0

Not a Bug

5

Test tool defect

0

Test Environment

0

Tester error (mistake)

0

※ Describe the QA start conditions and quality objectives of QA test phase set during the planning; and enter reasons of not measuring or not following them.

2. Test result summary and QA comment

※ Summarize test results and briefly describe QA comments.

If functionality/performance/security tests are not done, the description should include the reasons of non-execution.

※ If not relevant, put N/A in the field (N/A means not applicable to the project).

Test Type

Brief description of known key issues as per test results

Result of Functional Test

Finished function test, 34 defects were reported ,18 defects were fixed, 9 defects were marked postponed status

Result of Performance Test

Pass

Known Issue

9 defects were maked as postponed for the reason return values by CCI were not correct
APIS-56: Data will be inserted into local machine when ip is "00.00.00.00"
APIS-57: Result of inserting "NULL values" into table isn't correct.
APIS-66: Method of execute() can't support bit type
APIS-68: Precision's return values about int, float and numeric are not correct
APIS-69: Scale method only return zero value for all column
APIS-81:Method foreign_key_info can't support three parameters form
APIS-82: Values of DELETE_RULE and UPDATE_RULE are not correct of foreign_key_info method
APIS-83: Error appear when inquiring column_info information about set, multiset and sequence
APIS-153: Segment default will appear of cubrid_st_lob_export () method