tangle-accelerator
tangle-accelerator copied to clipboard
DLTcollab
CI: Setup testing IRI environment
We currently use public network to process CI which causes transaction hashes disappear and hard to implement MAM unit test. Therefore, we may use docker to setup a IRI with fixed DB.
I try to use the IRI docker, but it takes about 3-4 mins to startup and cost about 2.27G memory.
Maybe we could change the test case to avoid using the same transaction hash, for example, we could send the transaction to get the new transaction hash, then using the new transaction hash to fetch the transaction. 🤔
If we don't want to interact with the mainnet, maybe we just need the testnet.
testnet is absolutely OK for me. So even we used testnet, does IRI still take 4 mins to setup?
It is my suggestion, start the IRI testnet all the time, and use it to check the test case, so we don't need 4 mins to startup or setup. And we may need to change the test case to avoid the IRI local snapshot. 🤔
We currently run CI on private tangle. It enables us to send value tranasctions.
@junwei0117 Do you think that the current way that run CI totally on private tangle is a good choice. If so, I will close this issue
@HowJMay I think that is a good solution because any reaction of the private tangle is exactly the same as the mainnet, but the only thing we need to worry about is the confirmation of the transaction, because there is not enough transaction on the private tangle to ensure that the transaction can be verified, unless we start the Spammer.
For some reason, I closed the private tangle and started a comnet node. Comnet is composed of only Hornet, and the Hornet behaviour is expected to be the same as the IRI.