Stages For The NuNet Public Alpha Testnet
Greetings NuNetopians,
NuNet is excited to announce the launch of its public alpha testnet release, which features a staged testing approach to ensure that individual components are working correctly.
The staged testing approach used by NuNet ensures that each component of the platform is working correctly before moving on to the next stage. This approach helps to identify and resolve issues early in the development process, which can save a significant amount of time and resources in the long run.
Here’s a brief overview of NuNet’s staged testing approach:
- Components Testing: In this stage, individual components of NuNet are tested in isolation to ensure they are working as expected. This includes testing functions, modules, and algorithms.
- Integration Testing: In this stage, components are tested in combination with each other to ensure that they work correctly when integrated into the overall system.
- System Testing: In this stage, the entire system is tested to ensure that it meets the requirements and specifications set out by NuNet.
By using a staged testing approach, NuNet can ensure that each component of its platform is working correctly before moving on to the next stage. This approach helps to minimize the risk of bugs and other issues that could impact the performance and reliability of NuNet.
NuNet’s public alpha testnet release is an exciting milestone for the platform and our community. We look forward to working with our users to continue to improve and evolve NuNet in the coming weeks.
Testing Schedule
Stage 1: Create wallet (using Nami or Eternl)
1.1 Objectives.
Stage 1 will focus on testing components in relation to creating test wallets and receiving mNTX that will be needed to perform other tests.
1.2 Testing Type
This testing campaign will be focused on component testing. We will test mNTX and Testnet wallet functions in isolation.
1.3 Scope of Testing
The following features and functionalities will be tested during this campaign
- Using PreProd Cardano Network — Ensuring the community is able to create a PreProd Cardano Wallet
- Adding tADA — Adding tADA to testers wallets
- mNTX workflow — Testing the workflow in place to monitor and track community wallets, GitLab and Discord Names to determine rewards.
- Adding mNTX — Adding mNTX to testers wallets
- Test community communication — Testing communication workflows between NuNet team and community testers
1.4 Testing schedule
This campaign will run from April 28th to May 1st.
1.5 Get Involved
Please join our Discord Server and head to #role-assignment click on 1️⃣ to be given access to the relevant testing channels.
In order to receive mNTX your wallet you will need to be added to our Testnet Whitelist to receive mNTX.
Stage 2: Onboard on NuNet
2.1 Objectives
Stage 2 will focus on testing components in relation to onboarding community devices to NuNet and the discovery of other devices on the network.
Before participating in this Staged Test please read the Testing Configuration page.
2.2 Testing Type
This testing campaign will be focused on component testing. We will test DMS installation and onboarding devices to NuNet.
2.3 Scope of Testing
The following features and functionalities will be tested during this campaign
- Installing the DMS on community devices
- Running the DMS CLI — This will test onboarding devices, managing resources, wallets, and interactions with peers.
- Onboarding using wallet address created in Stage 1
- Testing Network Status Dashboard 1
- Peer Discovery
2.4 Testing schedule
This campaign will run from May 1st to May 8th.
Stage 3: Act as a Compute Provider
3.1 Objectives
Stage 3 will focus on NuNet compute providers — deploying jobs, checking if they have run successfully and testing payments for jobs run on compute provider devices.
3.2 Testing Type
This testing campaign will be focused on integration testing. Verifying that different components or modules work together as expected for compute providers.
3.3 Scope of Testing
The following features and functionalities will be tested during this campaign:
- Installing the Compute Provider Dashboard (CPD)
- Set/change resource parameters using the DMS CLI so this machine can be chosen to run a ML job
- Testing job deployment — waiting and see/monitor if any job was deployed and run successfully on this machine
- Payments — Claiming the mNTX reward using the CPD and the wallet created on Stage 1
3.4 Testing schedule
This campaign will run from May 8th to 22nd in parallel with Stage 4 (Acting as a Service Provider).
Stage 4: Act as a Service Provider
4.1 Objectives
Stage 4 will focus on testing deploying jobs from the Service Provider Dashboard.
4.2 Testing Type
This testing campaign will be focused on integration testing. Verifying that different components or modules work together as expected for service providers.
4.3 Scope of Testing
The following features and functionalities will be tested during this campaign
- Installing the Service Provider Dashboard (SPD)
- Using the SPD and the wallet created on Stage 1 request to run a ML job (this will lock the mNTX funds)
- Waiting and checking to finish the ML job and review results
4.4 Testing schedule
This campaign will run from May 8th to 22nd in parallel with Stage 3 (Acting as a compute provider).
About NuNet
NuNet lets anyone share and monetize their computing resources, turning cloud computing power from a centralized service into an open protocol powered by blockchain. Find out more via:
