Skip to content

Explicit Red Car Condition Validation #234

@dchansen06

Description

@dchansen06

Being flagged as a red car is really bad for us, we need to setup HOOTL tests of some kind to verify our logic at no point in time will cause such an event (unless it is necessary)

This focuses on our TSSI lights during both normal operation and erroneous non-red-car operations

Last year we witnessed a red car condition when flashing their firmware for example, we need to be able to say with certainty that (if the hardware is correct) our code will not produce incorrect TSSI values

It is recommended to have both HOOTL tests and other (runtime? compile time?) checks on this

As part of this we should probably test that if something goes wrong #129 we still enter red car conditions

Metadata

Metadata

Labels

3 NORMALImportant but not really a priorityBig FrySomething that is complex and/or largeBoardsRelated to or involving any physical boardsCTestAnything related to or dealing with CTestDocumentationImprovements or additions to documentationEnhancementNew feature or requestHOOTL TestingHaving to do with or interacting with HOOTL testingPeripheralRelated to or involving a peripheral including abstractionsSensorsSomething involved with or related to sensors

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions