CUBRID PHP 8.4.1.0004 QA Test Report

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

N/A

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%

88%

One cci bug CUBRIDSUS-8294 is active.
Two cases were caused by this CCI problem.
APIS-199: caused by CUBRIDSUS-8294
APIS-198: caused by CUBRIDSUS-8294
APIS-193: need for futher research
APIS-191: error information is not correct  

QA test code coverage

70%

82.1%

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

13

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

Active

4

Closed

9

Detailed information of closed defects (#)

Fixed

7

Won't Fix

2

Cannot reproduce

0

PostPoned

0

Roll back

0

PostPone

0

By design

0

Not a Defect

Duplicate

0

Not a Bug

0

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
   a) 13 defects were reported
   b) 7 defects were fixed
   c) 2 defects were caused by cci(APIS-199, APIS-198)
   d) APIS-193: need for futher research
   e) APIS-191: error information is not correct

Result of Performance Test 

Known Issue 

1. cubrid_lob2_write() function can only append data to lob object.
   reason: the resolution of CUBRIDSUS-8145 is by design.
       the bug is about cci_blob_write or cci_clob_write function can't override or change the content of existing lob objectthe resolution of CUBRIDSUS-8145 is by design.
2. Two bugs are still active for the reason that cci bugs CUBRIDSUS-8294
   APIS-199：Exporting file of cubrid_lob2_export() will fail after using cubrid_lob2_write()
   APIS-198：Size of lob object isn't correct after using cubrid_lob2_write()
   CUBRIDSUS-8294： the value returned by cci_clob_size will not be updated after executing appending using cci_clob_write function