CUBRID PHP 8.4.1 QA Test Report

Product QA done by

Cubrid QA Team

QA participants

Zou Jing, Guo Rui

QA test duration

2012.02.27~ 2012.03.19

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)

-

2731

Unit test code coverage (%)

70%

73.10%

# of critical errors at the static analysis

0%

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%

87%

Eight cci bugs are active
CUBRIDSUS-7159
CUBRIDSUS-7160
CUBRIDSUS-7161
CUBRIDSUS-7165
CUBRIDSUS-7167
CUBRIDSUS-7170
CUBRIDSUS-7174
CUBRIDSUS-7178
14 failed cases were caused by cci problem.

QA test code coverage

70%

87.5%

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

27

Eight cci bugs are active
CUBRIDSUS-7159
CUBRIDSUS-7160
CUBRIDSUS-7161
CUBRIDSUS-7165
CUBRIDSUS-7167
CUBRIDSUS-7170
CUBRIDSUS-7174
CUBRIDSUS-7178

Active

3

Closed

24

Detailed information of closed defects (#)

Fixed

6

Won't Fix

14

Cannot reproduce

1

PostPoned

0

Roll back

0

PostPone

0

By design

0

Not a Defect

Duplicate

0

Not a Bug

3

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

1. Finished function test, 27 defects were reported , 6 defects were fixed, 13 defects were caused by cci. Two defects were about modified the php cubrid manual. One defect was postponed to resolve in next version

Result of Performance Test

Base on the scope in report, test result is : Pass

Known Issue

13 defects were caused by cci.
Eight cci bugs are active.
- CUBRIDSUS-7159 : No errorr appeares when passing a invalid time to cci_bind_param() method
- CUBRIDSUS-7160: cci_bind_param() method can't support binding a value in binary mode
- CUBRIDSUS-7161: No error appears when passing a not correct parameter to cci_schema_info() method
- CUBRIDSUS-7165: Return value of cci_get_autocommit method is not zero when setting autocommit to off in cci_connect_with_url() method
- CUBRIDSUS-7167: Connect will not fail when passing a error db_user value to cubrid_connect_with_url() method
- CUBRIDSUS-7170: Error will appear when cci_cursor moved to bottom result set in asynchronous mode
- CUBRIDSUS-7174: Return value about INDEXED using cci_schema_info() method is not zero when column is reverse unique index or unique index
- CUBRIDSUS-7178: The return value about index column is reverse_index using cci_get_result_info() method