summaryrefslogtreecommitdiff
path: root/docs/newbs_testing_debugging.md
diff options
context:
space:
mode:
authorskullY <skullydazed@gmail.com>2020-02-20 15:50:50 -0800
committerskullydazed <skullydazed@users.noreply.github.com>2020-03-05 16:00:10 -0800
commita701c15d872ad171592335e61e91d7234dbec54a (patch)
treeef06fabdf0c0cd5d7457b63c48264700ac7fc67c /docs/newbs_testing_debugging.md
parent1b7fa46f8e0616450bed8bff71bc1cffbca2eac8 (diff)
Rework the newbs guide around the qmk cli
Diffstat (limited to 'docs/newbs_testing_debugging.md')
-rw-r--r--docs/newbs_testing_debugging.md10
1 files changed, 1 insertions, 9 deletions
diff --git a/docs/newbs_testing_debugging.md b/docs/newbs_testing_debugging.md
index 4756a29bec..62982584f4 100644
--- a/docs/newbs_testing_debugging.md
+++ b/docs/newbs_testing_debugging.md
@@ -4,15 +4,7 @@ Once you've flashed your keyboard with a custom firmware you're ready to test it
## Testing
-Testing your keyboard is usually pretty straightforward. Press every single key and make sure it sends the keys you expect. There are even programs that will help you make sure that no key is missed.
-
-Note: These programs are not provided by or endorsed by QMK.
-
-* [QMK Configurator](https://config.qmk.fm/#/test/) (Web Based)
-* [Switch Hitter](https://web.archive.org/web/20190413233743/https://elitekeyboards.com/switchhitter.php) (Windows Only)
-* [Keyboard Viewer](https://www.imore.com/how-use-keyboard-viewer-your-mac) (Mac Only)
-* [Keyboard Tester](http://www.keyboardtester.com) (Web Based)
-* [Keyboard Checker](http://keyboardchecker.com) (Web Based)
+Testing your keyboard is usually pretty straightforward. Press every single key and make sure it sends the keys you expect. You can use [QMK Configurator](https://config.qmk.fm/#/test/)'s test mode to check your keyboard, even if it doesn't run QMK.
## Debugging