@@ -94,6 +94,71 @@ websocket. Do this by going to `about:config` and setting the
9494Additionally you need to run with the `HTTPS` environment variable set to
9595`true`. Note that `npm run pilot` will handle this automatically.
9696
97+## Testing
98+
99+Automated tests for critical user journeys are coming Soon™️. Until then, here are several manual test cases to consider when making changes.
100+### Mnemonic Login
101+
102+"As a user, I can log into Bridge using a BIP39 mnemonic phrase"
103+
104+1. Click the 'Mnemonic, Metamask, Hardware Wallet ...' Button, then click 'Mnemonic (BIP 39)'
105+2. Paste the mnemonic above (in 'Useful Accounts') into the text area, then click 'Login'
106+3. Confirm that you are able to view the Points list view. Since no points have been created yet, you should see the following message:
107+> No points to display. This wallet is not the owner or proxy for any points.
108+
109+### Galaxy Creation
110+
111+"As a user, I can create a new galaxy"
112+
113+1. Once logged, in, click the "Create a Galaxy" button
114+2. Enter a test galaxy name, e.g. `~wep`, sign and send the transaction
115+3. Log out and back into Bridge, confirm that the newly created galaxy is rendered in the points list
116+
117+### Star Creation
118+
119+"As a user, I can create a new star"
120+
121+1. Once a galaxy has been created, click it in the points list
122+2. Click "Issue Point", enter one of the suggested star names, and sign and send the transaction
123+3. Log out and back into Bridge, confirm that the newly created star is rendered in the points list
124+
125+### Planet Creation
126+
127+"As a user, I can create a new planet"
128+
129+1. Once a star has been created, click it in the points list
130+2. Click "Issue Point", enter one of the suggested planet names, and sign and send the transaction
131+3. Log out and back into Bridge, confirm that the newly created planet is rendered in the points list
132+
133+### Invite Issuance
134+
135+"As a user, I can create a new invite"
136+
137+First, in `Bridge.js`, set the `INITIAL_NETWORK_TYPE` to Ropsten:
138+```js
139+const INITIAL_NETWORK_TYPE = NETWORK_TYPES.ROPSTEN;
140+```
141+
142+Then, in `tank.js`, set the port to `3011`:
143+```js
144+const baseUrl = 'https://gas-tank.urbit.org:3011';
145+```
146+
147+1. Ask one of the Collaborators of this project for an Invite code :)
148+
149+(If you're generating a code, don't forget to set `inviteMail.js` port to `:3012` for testnet)
150+
151+### Invite Acceptance
152+
153+"As a new Urbit user, I can set up a new ID with an activation code"
154+
155+1. On the Bridge landing page, click the small "Activate" link
156+2. Paste the Invite code from the previous test case, and click "Go"
157+3. Download the Passport file, then use the enclosed Master Ticket and ID to login to Bridge again
158+### Known Issues
159+
160+When testing the invite acceptance and login flow on Ropsten, some of the Azimuth API calls will fail (e.g., `getConditional`).
161+
97162## Releases
98163
99164To generate a release `bridge-$VERSION.zip` file, use a simple `npm run release`.