---
# System prepended metadata

title: 'TEST PLAN - Enforcing Web3 user storage capacity limits - first iteration #851'

---

# TEST PLAN - Enforcing Web3 user storage capacity limits - first iteration #851


Before we release this first iteration to Production, we should test all the scenarios on staging.

### Changing a user's storage limit
* We create a new account in the front end of https://web3.storage Staging environment
* We attribute a new storage limit (in bytes) to a user in https://admin-storage.pages.dev/ interface
* 

### Receiving a first notification
* Upload some files
* Change the storage limit to an amount so the user is >75% of the quota
* Run the CRON to see if this person is over the list

### Changing a user's storage limit > notifications stop
* 

---

### For reference: test steps from the epic:
1. Deploy to staging. (We can actually deploy to prod as well if we want, as the cron job config is only set up to run it on staging at the moment - see above.)
2. Create some user accounts for ourselves and upload/pin some files.
3. Use admin.storage to set our quotas to something low enough to reach the 75%/80%/etc limit.
4. Run the cron job manually via the GitHub UI (see [instructions](https://docs.github.com/en/github-ae@latest/actions/managing-workflow-runs/manually-running-a-workflow)).
5. Reduce our quotas again so that we go over the limit.
6. Manually trigger the cron again.
7. Check that we’ve received the right emails and that the list of users over their quota has been sent to support@web3.storage.


# Issues with Trigram PR

Context: Progress bar ticket wasn't working

## What's needed to go live
* Blocked helptext is not accurate. User can create tokens. - To test on staging
* To verify. Tags value are coming back with wrong value. - To test on staging

## What can be fixed later

* There are no tests in the code
* Types, annotations and documentation has not been updated.
* User quota usertag is no longer coming through
* Redundant calls to the db for something that's already fetched
* No review asked from PL or us. It was just created and merged in main - changing the web3/storage main branch

* They are pushing us to deploy, while no tests have been done


We have started a PR to fix & clean up, which will also touch admin.storage. 