diff --git a/docs/contributing/code-reviewing.md b/docs/contributing/code-reviewing.md
index b7931986e2..7d71f33f85 100644
--- a/docs/contributing/code-reviewing.md
+++ b/docs/contributing/code-reviewing.md
@@ -104,7 +104,7 @@ this?". Good choices include
   user input, and potential bugs that are likely for the type of
   change being made.  Tests that exclude whole classes of potential
   bugs are preferred when possible (e.g., the common test suite
-  `test_bugdown.py` between the Zulip server's [frontend and backend
+  `test_markdown.py` between the Zulip server's [frontend and backend
   Markdown processors](../subsystems/markdown.md), or the `GetEventsTest` test for
   buggy race condition handling).
 
diff --git a/docs/subsystems/markdown.md b/docs/subsystems/markdown.md
index 08873ccb29..769a4ca9d1 100644
--- a/docs/subsystems/markdown.md
+++ b/docs/subsystems/markdown.md
@@ -33,7 +33,7 @@ message is sent).  As a result, we try to make sure that
 ## Testing
 
 The Python-Markdown implementation is tested by
-`zerver/tests/test_bugdown.py`, and the marked.js implementation and
+`zerver/tests/test_markdown.py`, and the marked.js implementation and
 `markdown.contains_backend_only_syntax` are tested by
 `frontend_tests/node_tests/markdown.js`.
 
@@ -79,7 +79,7 @@ testcases in `markdown_test_cases.json` that you want to ignore. This
 is a workaround due to lack of comments support in JSON. Revert your
 "ignore" changes before committing. After this, you can run the frontend
 tests with `tools/test-js-with-node markdown` and backend tests with
-`tools/test-backend zerver.tests.test_bugdown.BugdownTest.test_bugdown_fixtures`.
+`tools/test-backend zerver.tests.test_markdown.BugdownTest.test_bugdown_fixtures`.
 
 ## Changing Zulip's markdown processor
 
diff --git a/docs/testing/testing.md b/docs/testing/testing.md
index 38d751b457..18283542a0 100644
--- a/docs/testing/testing.md
+++ b/docs/testing/testing.md
@@ -33,7 +33,7 @@ typically involve running subsets of the tests with commands like these:
 
 ```
 ./tools/lint zerver/lib/actions.py # Lint the file you just changed
-./tools/test-backend zerver.tests.test_bugdown.BugdownTest.test_inline_youtube
+./tools/test-backend zerver.tests.test_markdown.BugdownTest.test_inline_youtube
 ./tools/test-backend BugdownTest # Run `test-backend --help` for more options
 ./tools/test-js-with-casper 09-navigation.js
 ./tools/test-js-with-node utils.js
diff --git a/tools/test-backend b/tools/test-backend
index 3513243a99..a4073d0348 100755
--- a/tools/test-backend
+++ b/tools/test-backend
@@ -196,12 +196,12 @@ def main() -> None:
 
     usage = """test-backend [options]
     test-backend # Runs all backend tests
-    test-backend zerver.tests.test_bugdown # run all tests in a test module
-    test-backend zerver/tests/test_bugdown.py # run all tests in a test module
-    test-backend test_bugdown # run all tests in a test module
-    test-backend zerver.tests.test_bugdown.BugdownTest # run all tests in a test class
+    test-backend zerver.tests.test_markdown # run all tests in a test module
+    test-backend zerver/tests/test_markdown.py # run all tests in a test module
+    test-backend test_markdown # run all tests in a test module
+    test-backend zerver.tests.test_markdown.BugdownTest # run all tests in a test class
     test-backend BugdownTest # run all tests in a test class
-    test-backend zerver.tests.test_bugdown.BugdownTest.test_inline_youtube # run a single test
+    test-backend zerver.tests.test_markdown.BugdownTest.test_inline_youtube # run a single test
     test-backend BugdownTest.test_inline_youtube # run a single test"""
 
     parser = argparse.ArgumentParser(description=usage,
diff --git a/zerver/tests/test_bugdown.py b/zerver/tests/test_markdown.py
similarity index 100%
rename from zerver/tests/test_bugdown.py
rename to zerver/tests/test_markdown.py