- Overview
- Guides
- Concepts
- Considerations And Constraints
- Absolute File References
- Assembly Colocation Assumptions
- Concurrent Use Of Test Resources
- Cross Application Domain Testing
- Heavily Executed Code Under Test
- Implicit File Dependencies
- Multi Threaded Tests
- Netstandard Test Projects
- Project Atomicity
- Project Build Platform And Configuration
- Rdi Data Point Location
- Test Atomicity
- Unique Test Names
- Using NCrunch With Source Control
- Reference
- Global Configuration
- Overview
- Auto Adjust Clashing Marker Colours
- Build Log Verbosity
- Build Process Memory Limit
- Capabilities Of This Computer
- Coverage Marker Style
- Cpu Cores Assigned To NCrunch Or Ide
- Custom Environment Variables
- Disable Global Hotkey
- Engine Hosting Strategy
- Fast Lane Threads
- Fast Lane Threshold
- Grid Maximum Reconnection Attempts
- Grid Reconnection Delay
- Impact Detection Mode
- Listening Port
- Log To Output Window
- Logging Verbosity
- Marker Colours
- Max Failing Test Trace Log Size
- Max Number Of Processing Threads
- Max Passing Test Trace Log Size
- Max Test Runners To Pool
- NCrunch Tool Window Colors
- Node Id (Name)
- Password
- Performance Aggregation Type
- Performance Display Sensitivity
- Pipeline Optimisation Priority
- Rdi Storage Settings
- Sliding Build Delay
- Snapshot Storage Directory
- Solution Storage Data Limit
- Spinner Colours
- Terminate Test Runners On Complete
- Test Process Memory Limit
- Tests To Execute On This Machine
- Text Output Font
- Workspace Base Path
- Solution Configuration
- Overview
- Additional Files For Grid Processing
- Additional Files To Include
- Allow Parallel Test Execution
- Allow Tests In Parallel With Themselves
- Infer Project References Using Assembly
- Instrumentation Mode
- NCrunch Cache Storage Path
- Only Consider Tests Outofdate If Impacted
- Project Config File Storage Path
- Show Coverage For Tests
- Show Metrics For Tests
- Tests To Execute Automatically
- Project Configuration
- Overview
- Additional Files To Include
- Allow Dynamic Code Contract Checks
- Allow Static Code Contract Checks
- Analyse Line Execution Times
- Autodetect Nuget Build Dependencies
- Build Priority
- Build Process Cpu Architecture
- Build Sdk
- Collect Control Flow During Execution
- Consider Inconclusive Tests As Passing
- Copied Project Dependencies
- Copy Referenced Assemblies To Workspace
- Custom Build Properties
- Data Storage File Size
- Default Test Timeout
- Detect Stack Overflow
- Enable Rdi
- Files Excluded From Auto Build
- Framework Utilisation Types
- Ignore This Component Completely
- Implicit Project Dependencies
- Include Static References In Workspace
- Instrument Output Assembly
- Method Data Limit
- Ms Test Thread Apartment State
- Preload Assembly References
- Prevent Signing Of Assembly
- Proxy Process File Path
- Rdi Cache Size
- Required Capabilities
- Restrict Tostring Usage
- Run Pre Or Post Build Events
- String Length Limit
- Track File Dependencies
- Use Build Configuration
- Use Build Platform
- Use Cpu Architecture
- Runtime Framework
- Overview
- Atomic Attribute
- Category Attribute
- Collect Control Flow Attribute
- Distribute By Capabilities
- Duplicate By Dimensions
- Enable Rdi Attribute
- Environment Class
- Exclusively Uses Attribute
- Inclusively Uses Attribute
- Isolated Attribute
- Method Data Limit Attribute
- Requires Capability Attribute
- Restrict Tostring Attribute
- Serial Attribute
- String Length Limit Attribute
- Timeout Attribute
- Uses Threads Attribute
- Global Configuration
- Troubleshooting
- Tools
- Keyboard Shortcuts
- Manual Installation Instructions
RDI Inline Directives
The behaviour of NCrunch RDI can be controlled for blocks of code using inline comments, in a similar manner to code coverage suppression comments.
This allows RDI data collection to be tuned to specific regions that benefit from higher data limits, or perhaps need to have RDI disabled for performance or compatability reasons.
Inline directives follow a specific pattern in the code. They start with a comment indicating the setting change required, then usually end with another comment restoring the setting to its default value.
public class InlineDirectiveExample { //ncrunch: rdi off public void ThisMethodHasRdiDisabled() { Console.WriteLine("No RDI data collection"); } //ncrunch: rdi default //ncrunch: method data limit unlimited public string ThisMethodHasNoDataLimit() { StringBuilder result = new StringBuilder(); for (int i = 0; i < 100000; i++) result.Append("All of this data is collected and will be available in the RDI overlay"); return result.ToString() } //ncrunch: method data limit default //ncrunch: string length limit 30 public string ThisMethodHasACustomStringLengthLimit() { StringBuilder result = new StringBuilder(); result.Append("The length of this string will be limited to 30 characters when captured and reported by RDI"); return result.ToString() } //ncrunch: string length limit default }
When no closing comment is used to restore the setting to default, the setting change remains in place for the rest of the source file.
Available Directives
The following RDI inline directives are available:
- rdi off: Disables RDI for the code region
- rdi on: Enables RDI for the code region. Note that this will not enable RDI if it has been switched off using the Enable RDI config setting.
- rdi default: Restores RDI enable/disable to the default setting
- method data limit unlimited: Disables the RDI method data limit for the code region
- method data limit (size): Sets the RDI method data limit to the specified size (in bytes) for the code region
- method data limit default: Restores the default RDI method data limit
- string length limit unlimited: Disables the RDI string length limit for the code region
- string length limit (size): Sets the RDI string length limit to the specified size (in chars) for the code region
- string length limit default: Restores the default RDI string length limit