Skip to content

Conversation

@neacsu
Copy link
Contributor

@neacsu neacsu commented Jul 18, 2024

No description provided.

@vercel
Copy link

vercel bot commented Jul 18, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
nym-explorer ⬜️ Ignored (Inspect) Visit Preview Jul 23, 2024 5:14pm
nym-next-explorer ⬜️ Ignored (Inspect) Visit Preview Jul 23, 2024 5:14pm

@neacsu neacsu force-pushed the feature/bandwidth_limitation branch from a7da84e to 90fa20c Compare July 19, 2024 13:01
@benedettadavico benedettadavico added this to the TopDeck milestone Jul 23, 2024
@neacsu neacsu modified the milestones: TopDeck, Caramello Jul 23, 2024
@neacsu neacsu requested a review from octol July 23, 2024 17:16
@neacsu neacsu merged commit fd1d437 into develop Jul 23, 2024
@neacsu neacsu deleted the feature/bandwidth_limitation branch July 23, 2024 18:49
@neacsu neacsu modified the milestones: Caramello, TopDeck Jul 24, 2024
@tommyv1987
Copy link
Contributor

Scenario 1: Bandwidth Decreasing Continuously

Testing Completion Date: 31/07/2024

Testing Steps Performed:

  1. Started the client and noted the initial bandwidth (e.g., 1GB).
  2. Used the client and tracked bandwidth usage over time (e.g., decrease by 100MB every hour).
  3. Restarted the client after some usage.
  4. Verified the bandwidth continued from the last recorded value, not reset.

Validation:

  • Test Passed
  • Issues Found (Please specify below)

Notes (if any):
The bandwidth continued decreasing without resetting upon restart. Logs and reports correctly reflected the decreasing bandwidth.

Attachments (if applicable):
No attachments provided.


Scenario 2: Bandwidth Reset Next Day

Testing Completion Date: 31/07/2024

Testing Steps Performed:

  1. Used the client normally until the end of the day.
  2. Suspended some clients and kept others active.
  3. Checked bandwidth at midnight.
  4. Verified that bandwidth reset to 1GB for both suspended and active clients.

Validation:

  • Test Passed
  • Issues Found (Please specify below)

Notes (if any):
Bandwidth reset to 1GB for all clients at midnight. Logs and reports correctly showed the reset.

Attachments (if applicable):
No attachments provided.


Scenario 3: Bandwidth Reset at a Different Time (e.g., Midday)

Testing Completion Date: 31/07/2024

Testing Steps Performed:

  1. Configured the system to reset bandwidth at midday.
  2. Used the client and monitored bandwidth until midday.
  3. Kept the client connected during the reset time.
  4. Verified that bandwidth reset to 1GB live at midday.

Validation:

  • Test Passed
  • Issues Found (Please specify below)

Notes (if any):
Bandwidth reset to 1GB at midday while the client was connected. Logs and reports correctly reflected the reset.

Attachments (if applicable):
No attachments provided.


Scenario 4: Stale Check for 3 Days

Testing Completion Date: 31/07/2024

Testing Steps Performed:

  1. Kept a client inactive for 3 days.
  2. Verified removal from the peer list after 3 days.
  3. Reconnected the client after 3 days and checked for a new private IP.
  4. Restarted a client within 3 days and verified it retained the same private IP.

Validation:

  • Test Passed
  • Issues Found (Please specify below)

Notes (if any):
The client was removed from the peer list after 3 days of inactivity. Upon reconnection after 3 days, the client received a new private IP. The client retained the same private IP when restarted within 3 days.

Attachments (if applicable):
No attachments provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants