Best practices
Welcome to the Hydranet Alpha testing phase during which we will test the core features of the Hydranet Alpha build, including:
- Off-chain atomic swaps
- Off-chain liquidity rentals
- State channel backup service
- Off-chain liquidity pools
This is also an opportunity to revisit and test earlier features, such as on- and off-chain payments, our browser off-chain nodes, and more. Your efforts are essential in ensuring our platform’s seamless performance as we take this step forward.
System testing is challenging. The design space is often vast, with an almost infinite number of scenarios to explore. If we can’t test every single one of these scenarios, how do we ensure that everything runs smoothly, every time? This paradox is at the heart of system testing: finding the balance where we’ve tested enough to be confident in our platform’s reliability. With that said, in testing the Hydranet Alpha build, you have an important mission: to help us determine that point of confidence where we can take the next step in our development journey.
How alpha testing will work
We started on a small scale with a limited number of testers which was gradually increased until we reached the current stage - releasing the Alpha build to everyone. Together, we have and will continue to identify bugs and work through issues. The practicalities of this process will include:
- Dedicated Discord Channel
There will be a dedicated Discord channel for discussion on Hydranet's official Discord server. In this channel, you can ask questions, share insights, and discuss issues with team members and fellow Alpha testers. - Testnet faucet
There will be a dedicated Discord channel for testnet funds on Hydranet's official Discord server. In this channel, you can request testnet funds to be sent to your Hydranet wallet. Please return the funds when you're finished. - Pauses
There may be pauses in testing while fixes are implemented. Please trust that our developers are working diligently to resume testing as quickly as possible. - Iterative testing
Some features may need to be tested repeatedly as new solutions impact foundational parts of our platform. Patience and persistence are key. - Test in limited conditions
As testnet funds are expensive and sometimes hard to even get to, we focus on functionality instead of live/productive environment. So please keep swap amounts as low as possible - typically within the cent to dollar range. Otherwise large slippages can/will occur and the liquidity range may hit its upper or lower limits, which may require manual intervention to reset.
In short, we can say that our testing of Hydranet in its current stage is based on the following pillars:
- Functional testing
Ensuring that all features work as expected - creating/importing wallets, on- and off-chain payments, off-chain transfers, channel rentals, off-chain swaps, state channel backups. - Security testing
Verifying that funds remain safe during wallet use. - Performance testing
Ensuring the DEX and underlying protocols handle simultaneous transactions and high loads without degradation. - Regression testing
Confirming that new features and fixes don’t disrupt existing functionality.
Best practices for effective testing
During testing, be thorough and document your steps. For our developers to resolve issues effectively, they typically need to replicate them. Proper documentation of your steps leading up to the issue is therefore beneficial. So are screenshots of your results and possible error codes. When you report an issue, the following information will typically be asked from you, so keep this in mind:
- Short bug description
Give a brief description of the problem. For instance: Lithium channel balance does not update after swaps - Steps to reproduce
How can we reproduce the issue? For instance: Fund a wallet with ETH, rent a $10 worth of BTC Lightning channel and deposit $10 worth of ETH to a Lithium channel, swap your ETH for BTC, Lightning channel balance will update but Lithium channel balance will not. - What was expected to happen?
Describe what you would expect to happen following the steps above. For instance: I would expect the Lithium channel balance to update after my swap. Outbound liquidity (Can Send) should decrease to $0 while inbound liquidity (Can Receive) should increase to $10. - What actually happened?
Describe what actually happened when you followed the steps above. For instance: My Lithium channel did not change at all. My outbound liquidity remains at $10 worth of ETH and my inbound liquidity at $0. - System info
Add your system and browser information. An easy way to find these is by running the following command in a terminal:
npx envinfo --system --npmPackages hydra-node --binaries --browsers
To run this command, you may need to install Node.js, which can be downloaded from their official website. - Error codes
Check for any error codes and include these. Error codes can be found by right clicking on the screen, then selecting inspect. A window will open on the right-hand side of your screen. Navigate to the console tab and look for any error codes. An example is included below.
To report a problem, whether it be a bug or suggestion, there will be a button at the top of the Alpha Testnet channel on discord. Click the button to open a support ticket and follow the instructions. Wait for a response from our developers, as they may request additional information from you. If you’re unsure whether the actual outcome from one of your tests is expected or not, discuss it with your fellow Alpha testers and team before opening a support ticket.
Concluding words
As mentioned earlier, system testing is challenging and comprehensive. Creativity is your best ally. Don’t just test what you know is working, also try what you think shouldn’t work. How the platform handles errors and unexpected use is just as important, as this directly impacts the overall quality and user experience.
To assist you in your testing, we’ve created guides to demonstrate nominal use of our platform and for you to get acquainted with it. Don’t hesitate to go beyond these examples in your testing.
Happy testing!