Contribution Guidelines
en-cg
en-cgko-cg
en-cg
en-cgko-cg
  • Overview
  • Preface
    • How to Read This Document
  • Workflow with JIRA Issues
    • Introduction
    • Open: Register a JIRA issue
    • Confirmed: Issue Triage
    • Analysis, Develop: Progress of Work
    • Handover: Cleaning Up the Task
    • Resolved: Completing the Task
    • Test: Testing
    • Backport: Backporting
    • Closed: Terminating Issues
  • Workflow with Github
    • Introduction
    • Git Workflow
    • Git Branch Model
    • Feature Branch
    • Pull Request, Code Review, Code Merge
    • Backport
  • Workflow after Code Merging
    • Checking the QA Report
    • Procedure Guide in case of Test Failure (Regression)
    • Manual Creation Guide
  • Contributing Guideline for First Contributors
    • Contributor License Agreement (CLA)
    • Good first issue
    • Communication Channel
  • Release
    • Release
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Workflow after Code Merging

Checking the QA Report

PreviousBackportNextProcedure Guide in case of Test Failure (Regression)

Last updated 10 months ago

Was this helpful?

The QA team uses a CI tool called Jenkins to run the test system. When the Pull Request is merged, Jenkins is connected to Github and automatically tests the merged commit. (Reference: http://ci.cubrid.org/blue/organizations/jenkins/cubrid/activity/)

All tests are performed in Jenkins, and the result report is available at http://qahome.cubrid.org/. On the left side of the page, you can see the test result report by version and a summary of the latest test report is displayed on the right side.

If you click the test result report on the left, there is a tab as shown in the figure below. Each shows the results of testing for function, performance, and memory leaks. (The button on the first right 'verify status' is not used by the development team).

Meanwhile, QA test reports are sent periodically by email if you register in the developer mailing lists.

Make sure to check for functional tests, performance tests, and memory leaks when merging. In particular, if the performance test degrades by more than 5%, it is necessary to see if there is a problem.

The test is divided into a functional test and a non-function test. In terms of the functional tests, we are conducting tests for Linux and Windows environments respectively. Windows currently test fewer items than Linux.