When writing tests against sandbox merging, sometime a merge creates a node or edge with a new UUID.

It can be hard to write tests against this because I can't predict the UUID. I can't write a test which says: "merge node X into Workflow W and ensure that X has THIS UUID".

This must be a problem inside Lightning tests too?

This affects me most in the CLI mix task.

The best way I can think to solve this is to pass in a preordained list of new UUIDs against node names. Before creating a new UUID, Lightning should always check against this list and use the mapped values. I use a similar pattern in CLI testing and it works well

I think CLI has the same problem btw