Currently test-zeekoe.py only makes sure that an error doesn't occur when initiating the different flows that are tested. This ensures that the operations broadcasted in the test were valid and successful.
However, the tests don't verify that the customer or merchant daemons respond appropriately. What is missing from the test is making sure that zeekoe responds appropriately, e.g. that custClaim gets broadcasted after custClose, or that the merchant calls merchDispute on a revoked state. Currently you'd have to manually check the contract on chain to verify that the channel closed successfully.
Currently test-zeekoe.py only makes sure that an error doesn't occur when initiating the different flows that are tested. This ensures that the operations broadcasted in the test were valid and successful.
However, the tests don't verify that the customer or merchant daemons respond appropriately. What is missing from the test is making sure that zeekoe responds appropriately, e.g. that custClaim gets broadcasted after custClose, or that the merchant calls merchDispute on a revoked state. Currently you'd have to manually check the contract on chain to verify that the channel closed successfully.