search

ethersphere / bee-backlog

zenhub epics repo
0 stars 0 forks source link

Testing brainstorming #73

Open nikipapadatou opened 8 months ago

nikipapadatou commented 8 months ago

The following document focuses on a draft approach regarding the testing strategy. Each team of the organisation (where relevant) is called to brainstorm, discuss and get the appropriate tasks. Also, they are called to suggest improvements for the other teams whenever there is a dependency.

https://hackmd.io/mUhde0eDRryKOjjUmN1huA?view

This is a placeholder task for the bee team, where all the members are called to express their opinions on what we should focus on the tests. Feel free to create a replicate document and write there your comments, improvements, ideas and the relevant tasks.

Please, attach your documents in the comments.

mrekucci commented 8 months ago

https://hackmd.io/@ethswarm/rkiiXGEbT

ldeffenb commented 8 months ago

https://hackmd.io/@ethswarm/rkiiXGEbT

This might be ok in bee-backlog, but the main bee repository issues?

image

tmm360 commented 8 months ago

I agree, please don't use references to private contents on public repos. Actually, I would like to access documents also in the backlog area, anyway...

janos commented 8 months ago

My contribution to the testing brainstorming https://hackmd.io/SfY2ukFlSrqW6cqEv0w05Q?view.

notanatol commented 7 months ago

(updated) https://hackmd.io/7FDkHvB7QYi4MmgqNAgmCg

n00b21337 commented 3 months ago

As we don't have a clear path on how to move/arrive to swarm Testnet I will try to establish it now. I would agree that testnet should be treated as a place for deploying code that is expected to fully work and ideally isn't having any problems. Hence, as the last line of "defense" before mainet and release, not something where we iterate and try things out.

Having said that we do need to try out smart contracts integrated with bee nodes somewhere. So as we built this new hardhat replacement for docker, what Vandot and I talked about is that we then make a cluster using that with geth node where contracts are deployed and some rounds are played(few days?). Calling this "Pretesnet" for lack of better words, feel free to suggest better. With this we would try out contracts with bee nodes, and see if deployment and game are running smoothly, after checking this and signing off by both teams we can go to the next step and add this to Testnet.

ldeffenb commented 3 months ago

IIRC, there are config parameters to override the hard-coded contract addresses for a bee node at runtime. Could those be used, along with an appropriate bootnode, to allow folks outside the cluster to join the contract testing before formal testnet deployment? Or is the cluster 100% self-contained with its own private blockchain and not actually deploying the test contracts on sepolia?