Add a Fabric-X network test script under e2e-network/docker, for example e2e-network/docker/test-08-fabric-x.sh and wire it into the current test on push CI.
It should follow the structure of the existing network tests
The scenario should exercise Fabric-X the way a user does. From the temporary directory, run fablo.sh init fabric-x, fablo.sh validate, and fablo.sh up. After startup, assert that the generated Fabric-X artifacts are present and non-empty, at minimum config-block.pb.bin, shared_config.binpb, and client-tls-ca.pem, and verify the generated Fabric-X containers are healthy.
Then cover the namespace and lifecycle behavior: namespace list should work before namespace creation and show zero namespaces, namespace init should commit the default namespace, a later namespace list should show mynamespace, rerunning namespace init should be idempotent, rerunning up should skip artifact generation, stop and start should preserve a usable network, and reset should clear namespace state.
Add a Fabric-X network test script under e2e-network/docker, for example
e2e-network/docker/test-08-fabric-x.shand wire it into the current test on push CI.It should follow the structure of the existing network tests
The scenario should exercise Fabric-X the way a user does. From the temporary directory, run
fablo.sh init fabric-x,fablo.sh validate, andfablo.sh up. After startup, assert that the generated Fabric-X artifacts are present and non-empty, at minimumconfig-block.pb.bin,shared_config.binpb, andclient-tls-ca.pem, and verify the generated Fabric-X containers are healthy.Then cover the namespace and lifecycle behavior:
namespace listshould work before namespace creation and show zero namespaces,namespaceinit should commit the default namespace, a laternamespace listshould show mynamespace, rerunningnamespace initshould be idempotent, rerunningupshould skip artifact generation,stopandstartshould preserve a usable network, andresetshould clear namespace state.