Rewrite nds-bootstrap testing page

pages/_en-US/nds-bootstrap/faq.md

@@ -19,7 +19,7 @@ description: FAQ & Troubleshooting for nds-bootstrap
 - If the server says it's an nds-bootstrap issue, check if the game hasn't been reported already on [GitHub](https://github.com/DS-Homebrew/nds-bootstrap/issues) 
     - Check the closed issues too in case there has already been an issue closed in preference a different one. 
     - If it doesn't have any GitHub issue attached to it, go ahead and make a new one
-- If no solution has been found at this point, make sure you add it to the compatibility list.
+- If no solution has been found at this point, make sure you update the [compatibility list](https://wiki.ds-homebrew.com/nds-bootstrap/testing)
 
 #### Why are there issues with ROM loading, even though they're run natively?
 nds-bootstrap patches the ROM functions to run from an SD card, as the ROMs are hardcoded to read from Slot-1.

pages/_en-US/nds-bootstrap/testing.md

@@ -3,15 +3,27 @@ lang: en-US
 layout: wiki
 section: nds-bootstrap
 title: Compatibility List & Testing Tips
-description: Compatibility list and tips for testing games
+description: Compatibility list and tips for testing ROMs
 ---
 
 ### Compatibility List
-To view tested games, check the [compatibility list](https://docs.google.com/spreadsheets/d/1LRTkXOUXraTMjg1eedz_f7b5jiuyMv2x6e_jY_nyHSc/). If you want to contribute, press `View only` and then `Request edit access`.
+To view tested ROMs, check the [compatibility list](https://docs.google.com/spreadsheets/d/1LRTkXOUXraTMjg1eedz_f7b5jiuyMv2x6e_jY_nyHSc/). If you want to contribute, press `View only` and then `Request edit access`. Make sure to add entries to the proper sheet according to the tabs on the bottom of the page.
 
-### Tips For Testing Games
+To view ROMs with known issues, check the [issues page](https://github.com/DS-Homebrew/nds-bootstrap/issues) on Github. If you want to create a [new issue](https://github.com/DS-Homebrew/nds-bootstrap/issues/new), please properly follow the issue template.
-- Look for screen flickering or sound issues
+
-- If something looks off, run the game along a console not using nds-bootstrap to compare
+### Tips For Testing ROMs
-- Try as many features in the game as possible
+- Look through the [nds-bootstrap FAQ](https://wiki.ds-homebrew.com/nds-bootstrap/faq) to make sure that you understand how to troubleshoot issues
-- Try different settings for running the game (ARM9 CPU Speed, Card read DMA, Async card read, etc)
+- If testing for a specific reported bug, try to replicate the steps as close as possible
-- Be thorough
+    - If there are any differences (such as nds-bootstrap version, system used, or settings changed), make sure to include that in your report
+    - Feel free to ask the original reporter for more details (such as uploading a save file or any missing information) if possible
+    - If there is no solution, make sure to update the compatibility list
+- If a ROM has an issue after updating nds-bootstrap, try to find which specific version first introduced this issue
+    - You can downgrade nds-bootstrap by downloading a [past release](https://github.com/DS-Homebrew/nds-bootstrap/releases) and following the update instructions
+    - Downgrading to a past release of [TWiLight Menu++](https://github.com/DS-Homebrew/TWiLightMenu/releases) might be needed as well
+- If testing for a ROM that has no known issues or has not been tested before, try to be thorough
+    - Make sure to add the appropriate information on the compatibility list on the correct sheet
+    - Also make sure to remove games that have been tested off of the Testing Queue sheet
+- If testing to update blacklists, make sure to only change the blacklisted options
+    - The possible blacklisted options are 133 MHz (TWL) CPU Speed, Card Read DMA, Asynch Card Read, and SWI Halt Hook
+    - To enable blacklisted options in the per-game settings, go to `sd:/_nds/TWiLightMenu/settings.ini` and set `IGNORE_BLACKLISTS` to `1`
+    - If there are any issues caused when turning on these settings, please report them on the Github issues page