O-RAN Software Community
Spaces
Apps
Templates
Create
O-RAN SC
All content
Space settings
Shortcuts
O-RAN-SC Docs
O-RAN-SC Docs
This trigger is hidden
O-RAN-SC Gerrit
O-RAN-SC Gerrit
This trigger is hidden
O-RAN-SC Jira
O-RAN-SC Jira
This trigger is hidden
O-RAN SC
O-RAN SC
This trigger is hidden
TOC
TOC
This trigger is hidden
Projects
Projects
This trigger is hidden
Community
Community
This trigger is hidden
Releases
Releases
This trigger is hidden
Events
Events
This trigger is hidden
RSAC
RSAC
This trigger is hidden
Content
Results will update as you type.
•
Logo and Presentation Template
•
CLA
Project Developer Wiki
•
Signing Contributor License Agreement
•
O-RAN Developer's Guide to CI Resources and Processes at the LF
•
Tutorial: Making code contributions to O-RAN open source project
•
ORAN Base Docker Images for CI Builds
•
Packaging Libraries for Linux Distributions with CMake
•
Binary Repositories at PackageCloud.io
•
Configure Repo for Documentation
PTL/Committer Wiki
Best Practices
•
Table of Contents
•
Documentation
•
Jira
Licensing
•
Logging
•
Reporting Bugs
•
Unit Test Coverage
Core Infrastructure Initiative (CII) Badging
•
FAQ for Gerrit Access
•
INFO.yaml Guidelines
•
O1-Interface Data Models
•
Configure Sonar for C/C++
•
Participate/Engage in the O-RAN Software Community
•
Super Committers
•
O-RAN SC Committees
•
Partnerships
•
Presentations
•
Projects
File lists
•
How to Check in Large File(s) to Gerrit
Blogs
O-RAN SC
/
/
Best Practices
/
Unit Test Coverage
Summarize
Unit Test Coverage
Farheen Cefalu
Owned by
Farheen Cefalu
Aug 27, 2019
1 min read
Loading data...
The goal for projects is to use test-driven development and have excellent unit test coverage.
{"serverDuration": 38, "requestCorrelationId": "d40bb3a26f364b33a86cfc329bef6453"}