You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guide-release-testing.md
+56-68Lines changed: 56 additions & 68 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,10 @@ If any of those prerequisites is not met, the script should output a proper erro
86
86
87
87
If you need to build React Native from source, you can skip the `-c` parameter. By not passing the GitHub token, the script falls back to the previous flow, building everything locally.
88
88
89
-
## Dimensions to test (RN >= 0.79)
89
+
## Testing Sequence (RN >= 0.79)
90
+
91
+
> [!Tip]
92
+
> Make sure the remote assets are built on your release branch to use the `-c` option (highly recommended)
90
93
91
94
> [!Note]
92
95
> On React Native **`< 0.81`**`test-release-local` is called `test-e2e-local`
@@ -97,76 +100,127 @@ Here are the 4 dimensions we cover in manual testing:
adb uninstall com.rntestproject # delete RNTestProject from your Android emulator
118
133
```
119
134
120
-
## Dimensions to test (RN <= 0.78)
135
+
## Testing Sequence (RN <= 0.78)
136
+
137
+
> [!Tip]
138
+
> Make sure the remote assets are built on your release branch to use the `-c` option (highly recommended)
139
+
140
+
<details>
141
+
<summary>ℹ️ For (<b><code>RN < 0.71</code></b>) ℹ️<br/></summary>
142
+
You need to use the interactive script run you through the different variants below.
143
+
This script will ask you to select which platform and which project you want to test, and then to execute a series of extra steps during the process. Bear in mind, when testing RNTester on Android, you need to start the Android emulator ahead of time or it will fail.
144
+
145
+
```bash
146
+
./scripts/test-manual-e2e.sh
147
+
```
148
+
149
+
</details>
150
+
121
151
122
152
Here are the 8 dimensions we cover in manual testing:
3. Refer to the [spreadsheet of test cases](https://docs.google.com/spreadsheets/d/1p0Zs37ecau7Ty4L_4g1jf7PlivOmIEPjmDYq9Jp8qWI/edit?usp=sharing), make any outstanding notes in the Test Report
188
242
4. Close the Test Report issue if the release passes testing
189
-
190
-
### Recommended Sequence for testing
191
-
192
-
> [!Tip]
193
-
> Make sure the remote assets are built on your release branch to use the `-c` option (highly recommended)
194
-
195
-
> [!Note]
196
-
> On React Native **`< 0.81`**`test-release-local` is called `test-e2e-local`
197
-
198
-
```bash
199
-
react-native$ yarn test-release-local-clean # alias this command to make your life easier to something like "clean"
adb uninstall com.rntestproject # delete RNTestProject from your Android emulator
244
-
```
245
-
246
-
## Versions older than 71
247
-
248
-
You need to use the interactive script run you through the different variants in [Test Dimensions](#dimensions-to-test):
249
-
250
-
```bash
251
-
./scripts/test-manual-e2e.sh
252
-
```
253
-
254
-
This script will ask you to select which platform and which project you want to test, and then to execute a series of extra steps during the process. Bear in mind, when testing RNTester on Android, you need to start the Android emulator ahead of time or it will fail.
0 commit comments