Browse by Tag

architecture constraints developer diagnosis digital-twin dsl fault-injection field-based-testing field-data formal-verification fuzzing headless instrumentation isolation lifecycle logging model-based-testing monitoring noise-injection overhead performance postmortem privacy property-specification qa-team record-replay ros2 runtime-verification safety scenario-testing security simulation single-responsibility synchronization temporal-logic test-automation timing

architecture

• CD1. Developers should strive for ROS nodes with single responsibility

constraints

• CI1. Identify timing constraints
• CI2. Identify security and privacy constraints
• CI3. Identify safety constraints

developer

• CD1. Developers should strive for ROS nodes with single responsibility
• CD2. Ensure global time monotonicity of events and states
• CI1. Identify timing constraints
• CI2. Identify security and privacy constraints
• CI3. Identify safety constraints
• I1. Provide an API for querying and updating internal lifecycle
• I2. Provide an API for logging and filtering
• I3. Provide an API for injecting faults in execution scenarios
• I4. Isolate components for testing

diagnosis

• AR1. Perform postmortem analysis to diagnose non-passing test cases

digital-twin

• PE2. Create models for runtime assessment

dsl

• SDB2. Use Domain Specific Languages to Specify Properties

fault-injection

• I3. Provide an API for injecting faults in execution scenarios
• MTA1. Improve the robustness of the system by performing noise and fault injection

field-based-testing

• SE1. Use record-and-playback when performing exploratory field tests

field-data

• AR2. Use reliable tooling in order to manage field data

formal-verification

• PE2. Create models for runtime assessment
• SDB1. Property specification using a logic-based language

fuzzing

• MTA1. Improve the robustness of the system by performing noise and fault injection

headless

• SE2. No GUIs! Prioritize headless simulation

instrumentation

• I1. Provide an API for querying and updating internal lifecycle
• I2. Provide an API for logging and filtering
• I3. Provide an API for injecting faults in execution scenarios
• I4. Isolate components for testing

isolation

• I4. Isolate components for testing

lifecycle

• I1. Provide an API for querying and updating internal lifecycle

logging

• AR2. Use reliable tooling in order to manage field data
• I2. Provide an API for logging and filtering

model-based-testing

• PE2. Create models for runtime assessment

monitoring

• MTA2. Exploit automation for test case generation, test case prioritization and selection, oracle and monitor generation

noise-injection

• MTA1. Improve the robustness of the system by performing noise and fault injection

overhead

• PE1. Understand the overhead acceptance criteria

performance

• PE1. Understand the overhead acceptance criteria

postmortem

• AR1. Perform postmortem analysis to diagnose non-passing test cases

privacy

• CI2. Identify security and privacy constraints

property-specification

• SDB1. Property specification using a logic-based language
• SDB2. Use Domain Specific Languages to Specify Properties

qa-team

• AR1. Perform postmortem analysis to diagnose non-passing test cases
• AR2. Use reliable tooling in order to manage field data
• MTA1. Improve the robustness of the system by performing noise and fault injection
• MTA2. Exploit automation for test case generation, test case prioritization and selection, oracle and monitor generation
• PE1. Understand the overhead acceptance criteria
• PE2. Create models for runtime assessment
• SDB1. Property specification using a logic-based language
• SDB2. Use Domain Specific Languages to Specify Properties
• SDB3. Use languages and tools to scenario-based specification of test cases
• SE1. Use record-and-playback when performing exploratory field tests
• SE2. No GUIs! Prioritize headless simulation

record-replay

• SE1. Use record-and-playback when performing exploratory field tests

ros2

• CD2. Ensure global time monotonicity of events and states
• CI1. Identify timing constraints
• CI2. Identify security and privacy constraints
• I1. Provide an API for querying and updating internal lifecycle
• MTA1. Improve the robustness of the system by performing noise and fault injection

runtime-verification

• CI3. Identify safety constraints
• I4. Isolate components for testing
• MTA2. Exploit automation for test case generation, test case prioritization and selection, oracle and monitor generation
• SDB2. Use Domain Specific Languages to Specify Properties

safety

• CI3. Identify safety constraints

scenario-testing

• SDB3. Use languages and tools to scenario-based specification of test cases

security

• CI2. Identify security and privacy constraints

simulation

• SDB3. Use languages and tools to scenario-based specification of test cases
• SE2. No GUIs! Prioritize headless simulation

single-responsibility

• CD1. Developers should strive for ROS nodes with single responsibility

synchronization

• CD2. Ensure global time monotonicity of events and states

temporal-logic

• SDB1. Property specification using a logic-based language

test-automation

• MTA2. Exploit automation for test case generation, test case prioritization and selection, oracle and monitor generation

timing

• CD2. Ensure global time monotonicity of events and states
• CI1. Identify timing constraints