Components
Simscope builds on top of components, which are the base grouping. A Simscope component is the same in other terminology as units, blocks, or environments.
Components should ideally mirror your organizations' grouping.
They can be used to:
- Show all Regressions for a component.
- Show all Signatures for a component.
- Show Statistics (pass/fail, etc) for a component.
Component Fields
Components have three fields:
| Field | Description |
|---|---|
| Project | Projects link to source code Repository paths |
| Default Branch | Default branch field when creating a rule in this component |
| Inactive | Setting a component to inactive hides it from search dropdowns |
This allows Simscope to resolve Rules assigned to a component by:
- Look up the Rule's component
- Look up the Component's parent Project
- Look up the Project Repository
- Validate the Fix ID and Branch within the Repository
Naming
It is highly recommended to name your components with short, lowercase names.
This makes Rules easier to write, and signature filtering queries shorter.
Example Component Names
york_compressyork_fpuyork_gpioyork_cpuorleans_clusterorleans_full_chip
Editing/Hiding/Purging Components
See the Administration Guide for Components.