Automated state handling/testing strategy for nodes

[JimTharioAmazon]

Today we have several possible node states and many possible combinations depending on the type of service the node represents:

Alarming on/off (CW Alarms) Alerting fail/degraded/off (Media Alerts) Running state on/off (Describe, CW Events)

I'd like to come up with an automated testing strategy for verifying proper state display based on a matrix of state combinations and desired displayed state.

A couple of challenges here: Define the matrix of combinations and decide the best display for that case (team) Can we automate testing of the model/diagrams using something like Selenium and driven from this matrix?

Stretch: How do we use the same state matrix definition, captured as JSON or another structured format, to drive both state code generation for specific nodes and test generation for the front-end? Ex: can we make this declarative?

[JimTharioAmazon]

Can individual node state be managed with a small FSM attached to each node from Machina.js?

[Joaquin6]

we can address as a spike and combine ideas