Page Index - rdkcentral/ut-core GitHub Wiki
123 page(s) in this GitHub Wiki:
- Home
- UT-Core Framework
- Objectives for the framework
- Primary Objectives:
- Secondary Objectives
- Key Features
- Documentation
- ut-control
- Getting Started
- Running Tests
- Example of the unit test
- Using the -p profile_filename switch
- Contributing
- 1. Standards & Development Process Flow
- Please reload this page
- 1.0. Standards: Tier 1 Operator Guide: Branching for Direct Contributions
- Please reload this page
- 1.0.1 Standards: Tier 2 Operator Guide: Forking for External Contributions
- Please reload this page
- 1.1. Standards: Principles from Code Complete
- Please reload this page
- 1.2. Standards: Issue Description Guideline
- Please reload this page
- 1.3. Standards: Milestone Description Guideline
- Please reload this page
- 1.4. Standards: Commit Message: The 50‐72 Rule: A Simple Guide
- Please reload this page
- 1.5. Standards: Semantic Versioning and Testing Suite Alignment
- Please reload this page
- 2. Standards: Single Source of Truth ‐ HAL Interfaces and Testing Suites
- Please reload this page
- 2.1. Standards: Doxygen: Crafting Excellent Documentation
- Please reload this page
- 2.2. Standards: Forking And Branching
- Please reload this page
- 2.3. Standards: Performing Changes to an interface
- Please reload this page
- 2.4. Standards: Repository Access and Branch Protection Policy
- Please reload this page
- 2.5. Standards: Feature Branch Workflow
- Please reload this page
- 3. Standards: Levels of Test for Vendor Layer
- Please reload this page
- 3.0.1 Standards: Testing Feedback Loops
- Please reload this page
- 3.1. Standards: Overview of Test‐Driven Development
- Please reload this page
- 3.2. Standards: Requirements for building testing suites
- Please reload this page
- 3.2.1: Standards: Phased Delivery with Checkpoints
- Please reload this page
- 3.3. Standards: L4 ‐ System Interface Testing
- Please reload this page
- 3.4. Standards: L4: Vendor Full Stack ‐ Video ‐ Smoke Regression Test
- Please reload this page
- 4. Standards: Dynamic Library Loading for Vendor Abstraction
- Please reload this page
- 4.0.1: Standards: Dynamic Library Search Order
- Please reload this page
- 4.1. Standards: Dynamically Installable Plugins In C
- Please reload this page
- 5.0.1: Standards: vDevice Architecture Overview
- Please reload this page
- 5.0: Standards: vDevice Overview
- Please reload this page
- 5.1.0: Standards: vDevice Controller
- Please reload this page
- 5.1.1: Standards: vDevice Control Plane
- Please reload this page
- autogenerate.sh: Running the Framework Generation Script
- Please reload this page
- FAQ: QEMU vs Vagrant
- Please reload this page
- FAQ: Video and Audio Playback Performance Metrics
- Please reload this page
- FAQ: Black‐Box Testing and Code Coverage Metrics
- Please reload this page
- FAQ: Buildroot vs. Yocto Project vs. Bob the Builder
- Please reload this page
- FAQ: C Macro that prints structure fields
- Please reload this page
- FAQ: C macro that prints the function name, parameter names with values
- Please reload this page
- FAQ: Choosing GHEC‐ORG or RDKCentral
- Please reload this page
- FAQ: Comparing Python Development Platforms
- Please reload this page
- FAQ: Git Flow Support for Multiple mainlines
- Please reload this page
- FAQ: Git‐Flow: Developers Branching Model
- Please reload this page
-
FAQ: Migrating Binaries to
Git LFS - Please reload this page
- FAQ: RDK Docker Toolchain
- Please reload this page
- FAQ: Release Engineers: Performing a release with git flow
- Please reload this page
- FAQ: Sign up for RDK Central ‐ Tier 1 Registration
- Please reload this page
- FAQ: Software Post Release Development Cycle
- Please reload this page
- FAQ: UT Core Framework Overview
- Please reload this page
- FAQ: Vagrant: Setting Up and Managing Your Vagrant VM
- Please reload this page
- How to use UT‐Core to write a simple app in C or CPP using the ut‐core subsystem
- Please reload this page
- T1: Training: CODEOWNERS: Ensuring Code Quality and Governance
- Please reload this page
- UT Core Building using Docker or Vagrant
- Please reload this page
- ut_kvp: A Flexible Key‐Value Pair Framework
- Please reload this page
- ut_kvp_profile: Key‐Value Pair Assertions for Unit Testing
- Please reload this page
- UTCore: Test Group Support
- Please reload this page
- UT‐Core: Concept Overview: UT‐Core and Engineering Suites Integration
- Please reload this page
- UT‐Core: How to Build and Run a HAL Testing Suite
- Please reload this page
- vDevice: Overview
- Please reload this page