remove tests from this pr

Author: dojutsu-user

readthedocs/rtd_tests/tests/test_search_json_parsing.py

@@ -17,12 +17,7 @@ def test_h2_parsing(self):
                 'files/api.fjson',
             ),
         )
-        self.assertEqual(data['path'], 'api')
         self.assertEqual(data['sections'][1]['id'], 'a-basic-api-client-using-slumber')
-        self.assertTrue(data['sections'][1]['content'].startswith(
-            'You can use Slumber'
-        ))
-        self.assertEqual(data['title'], 'Read the Docs Public API')
-
-        for section in data['sections']:
-            self.assertFalse('\n' in section['content'])
+        # Only capture h2's after the first section
+        for obj in data['sections'][1:]:
+            self.assertEqual(obj['content'][:5], '\n<h2>')

readthedocs/search/tests/conftest.py

@@ -8,8 +8,6 @@
 
 from readthedocs.projects.models import Project, HTMLFile
 from readthedocs.search.documents import PageDocument
-from readthedocs.sphinx_domains.models import SphinxDomain
-
 from .dummy_data import ALL_PROJECTS, PROJECT_DATA_FILES
 
 
@@ -34,28 +32,6 @@ def all_projects(es_index, mock_processed_json, db, settings):
             file_name = file_basename + '.html'
             version = project.versions.all()[0]
             html_file = G(HTMLFile, project=project, version=version, name=file_name)
-
-            # creating sphinx domain test objects
-            file_path = get_json_file_path(project.slug, file_basename)
-            if os.path.exists(file_path):
-                with open (file_path) as f:
-                    data = json.load(f)
-                    domains = data['domains']
-
-                    for domain_data in domains:
-                        domain_role_name = domain_data.pop('role_name')
-                        domain, type_ = domain_role_name.split(':')
-
-                        G(
-                            SphinxDomain,
-                            project=project,
-                            version=version,
-                            html_file=html_file,
-                            domain=domain,
-                            type=type_,
-                            **domain_data
-                        )
-
             PageDocument().update(html_file)
 
         projects_list.append(project)
@@ -70,17 +46,12 @@ def project(all_projects):
     return all_projects[0]
 
 
-def get_json_file_path(project_slug, basename):
-    current_path = os.path.abspath(os.path.dirname(__file__))
-    file_name = f'{basename}.json'
-    file_path = os.path.join(current_path, 'data', project_slug, file_name)
-    return file_path
-
-
 def get_dummy_processed_json(instance):
     project_slug = instance.project.slug
     basename = os.path.splitext(instance.name)[0]
-    file_path = get_json_file_path(project_slug, basename)
+    file_name = basename + '.json'
+    current_path = os.path.abspath(os.path.dirname(__file__))
+    file_path = os.path.join(current_path, "data", project_slug, file_name)
 
     if os.path.exists(file_path):
         with open(file_path) as f:

readthedocs/search/tests/data/docs/story.json

@@ -0,0 +1,31 @@
+{
+  "content": "ReadtheDocsPhilosophy\nRead the Docs is Open Source software. We have licensed the code base as MIT, which provides almost no restrictions on the use of the code.\nHowever, as a project there are things that we care about more than others. We built Read the Docs to support  in the Open Source community. The code is open for people to contribute to, so that they may build features into https://readthedocs.org that they want. <h3>XSS exploit</h3> We also believe sharing the code openly is a valuable learning tool, especially for demonsrating how to collaborate and maintain an enormous website.\nOfficial website Support\nThe time of the core developers of Read the Docs is limited. We provide official developers support for the following things:\nLocal development on the Python code base\nUsage of https://readthedocs.org for Open Source projects\nBug fixes in the code base, as it applies to running it on https://readthedocs.org\nUnsupported\nThere are use cases that we don\u2019t support, because it doesn\u2019t further our goal of promoting  in the Open Source Community.\nWe do not support:\nSpecific usage of Sphinx and Mkdocs, that don\u2019t affect our hosting\nCustom s of Read the Docs at your company\n of Read the Docs on other platforms\nAny  issues outside of the Read the Docs Python Code\nRationale\nRead the Docs was founded to improve  in the Open Source Community. We fully recognize and allow the code to be used for internal installs at companies, but we will not spend our time supporting it. Our time is limited, and we want to spend it on the mission that we set out to originally support.\nIf you feel strongly about installing Read the Docs internal to a company, we will happily link to third party resources on this topic. Please open an issue with a proposal if you want to take on this task.",
+  "headers": [
+    "Unsupported",
+    "Rationale"
+  ],
+  "title": "Philosophy",
+  "sections": [
+    {
+      "content": "\nRead the Docs is Open Source software.\nWe have <a class=\"reference external\" href=\"https://github.com/readthedocs/readthedocs.org/blob/master/LICENSE\">licensed</a> the code base as MIT,\nwhich provides almost no restrictions on the use of the code.\n\nHowever,\nas a project there are things that we care about more than others.\nWe built Read the Docs to support  in the Open Source community.\nThe code is open for people to contribute to,\nso that they may build features into <a class=\"reference external\" href=\"https://readthedocs.org\">https://readthedocs.org</a> that they want.\nWe also believe sharing the code openly is a valuable learning tool,\nespecially for demonsrating how to collaborate and maintain an enormous website.\n",
+      "id": "read-the-docs-open-source-philosophy",
+      "title": "Read the Docs Open Source Philosophy"
+    },
+    {
+      "content": "\n<h2>Official Support<a class=\"headerlink\" href=\"#official-support\" title=\"Permalink to this headline\">\u00b6</a></h2>\n<p>The time of the core developers of Read the Docs is limited.\nWe provide official support for the following things:</p>\n<ul class=\"simple\">\n<li>Local development on the Python code base</li>\n<li>Usage of <a class=\"reference external\" href=\"https://readthedocs.org\">https://readthedocs.org</a> for Open Source projects</li>\n<li>Bug fixes in the code base, as it applies to running it on <a class=\"reference external\" href=\"https://readthedocs.org\">https://readthedocs.org</a></li>\n</ul>\n",
+      "id": "official-support",
+      "title": "Official Support"
+    },
+    {
+      "content": "\n<h2>Unsupported<a class=\"headerlink\" href=\"#unsupported\" title=\"Permalink to this headline\">\u00b6</a></h2>\n<p>There are use cases that we don\u2019t support,\nbecause it doesn\u2019t further our goal of promoting  in the Open Source Community.</p>\n<p>We do not support:</p>\n<ul class=\"simple\">\n<li>Specific usage of Sphinx and Mkdocs, that don\u2019t affect our hosting</li>\n<li>Custom  of Read the Docs at your company</li>\n<li> of Read the Docs on other platforms</li>\n<li>Any  issues outside of the Read the Docs Python Code</li>\n</ul>\n",
+      "id": "unsupported",
+      "title": "Unsupported"
+    },
+    {
+      "content": "\n<h2>Rationale<a class=\"headerlink\" href=\"#rationale\" title=\"Permalink to this headline\">\u00b6</a></h2>\n<p>Read the Docs was founded to improve  in the Open Source Community.\nWe fully recognize and allow the code to be used for internal installs at companies,\nbut we will not spend our time supporting it.\nOur time is limited,\nand we want to spend it on the mission that we set out to originally support.</p>\n<p>If you feel strongly about installing Read the Docs internal to a company,\nwe will happily link to third party resources on this topic.\nPlease open an issue with a proposal if you want to take on this task.</p>\n",
+      "id": "rationale",
+      "title": "Rationale"
+    }
+  ],
+  "path": "open-source-philosophy"
+}

readthedocs/search/tests/data/docs/support.json

@@ -1,49 +1,15 @@
 {
-    "path": "guides/wipe-environment",
-    "title": "Wiping a Build Environment",
-    "sections": [
-        {
-            "id": "wiping-a-build-environment",
-            "title": "Wiping a Build Environment",
-            "content": "Sometimes it happen that your Builds start failing because the build environment where the documentation is created is stale or broken. This could happen for a couple of different reasons like pip not upgrading a package properly or a corrupted cached Python package.In any of these cases (and many others), the solution could be just wiping out the existing build environment files and allow Read the Docs to create a new fresh one.Follow these steps to wipe the build environment:Click on the Edit button of the version you want to wipe on the right side of the page. Go to the bottom of the page and click the wipe link, next to the “Save” buttonBy wiping the documentation build environment, all the rst, md, and code files associated with it will be removed but not the documentation already built (HTML and PDF files). Your documentation will still online after wiping the build environment.Now you can re-build the version with a fresh build environment!"
-        }
-    ],
-    "domains": [
-        {
-            "role_name": "http:get",
-            "doc_name": "api/v3.html",
-            "anchor": "get--api-v3-users-(str-username)",
-            "type_display": "get",
-            "doc_display": "API v3",
-            "name": "/api/v3/users/(str:username)",
-            "display_name": ""
-        },
-        {
-            "role_name": "http:get",
-            "doc_name": "api/v3.html",
-            "anchor": "get--api-v3-projects-(string-project_slug)-versions-(string-version_slug)-",
-            "type_display": "get",
-            "doc_display": "API v3",
-            "name": "/api/v3/projects/(string:project_slug)/versions/(string:version_slug)/",
-            "display_name": ""
-        },
-        {
-            "role_name": "http:get",
-            "doc_name": "api/v3.html",
-            "anchor": "get--api-v3-projects-(string-project_slug)-versions-",
-            "type_display": "get",
-            "doc_display": "API v3",
-            "name": "/api/v3/projects/(string:project_slug)/versions/",
-            "display_name": ""
-        },
-        {
-            "role_name": "http:get",
-            "doc_name": "api/v3.html",
-            "anchor": "get--api-v3-projects-(string-project_slug)-",
-            "type_display": "get",
-            "doc_display": "API v3",
-            "name": "/api/v3/projects/(string:project_slug)/",
-            "display_name": ""
-        }
-    ]
+  "content": "ReadtheDocsWiping a Build Environment\nSometimes it happen that your Builds start failing because the build environment where the  is created is stale or broken. This could happen for a couple of different reasons like pip not upgrading a package properly or a corrupted cached Python package.\nIn any of these cases (and many others), the solution could be just wiping out the existing build environment files and allow Read the Docs to create a new fresh one.\nFollow these steps to wipe the build environment:\nGo to Versions\nClick on the Edit button of the version you want to wipe on the right side of the page\nGo to the bottom of the page and click the wipe link, next to the \u201cSave\u201d button\nNote\nBy wiping the  build environment, all the rst, md, and code files associated with it will be removed but not the  already built (HTML and PDF files). Your  will still online after wiping the build environment.\nNow you can re-build the version with a fresh build environment!",
+  "headers": [
+    "Wiping a Build Environment"
+  ],
+  "title": "Wiping a Build Environment",
+  "sections": [
+    {
+      "content": "\nSometimes it happen that your Builds start failing because the build\nenvironment where the  is created is stale or\nbroken. This could happen for a couple of different reasons like <code class=\"xref py py-obj docutils literal notranslate\"><span class=\"pre\">pip</span></code>\nnot upgrading a package properly or a corrupted cached Python package.\n\nIn any of these cases (and many others), the solution could be just\nwiping out the existing build environment files and allow Read the\nDocs to create a new fresh one.\n\nFollow these steps to wipe the build environment:\n\n\n<li>Go to <strong>Versions</strong></li>\n<li>Click on the <strong>Edit</strong> button of the version you want to wipe on the\nright side of the page</li>\n<li>Go to the bottom of the page and click the <strong>wipe</strong> link, next to\nthe \u201cSave\u201d button</li>\n\n\n\n<p class=\"first admonition-title\">Note</p>\n<p class=\"last\">By wiping the  build environment, all the <code class=\"xref py py-obj docutils literal notranslate\"><span class=\"pre\">rst</span></code>, <code class=\"xref py py-obj docutils literal notranslate\"><span class=\"pre\">md</span></code>,\nand code files associated with it will be removed but not the\n already built (<code class=\"xref py py-obj docutils literal notranslate\"><span class=\"pre\">HTML</span></code> and <code class=\"xref py py-obj docutils literal notranslate\"><span class=\"pre\">PDF</span></code> files). Your\n will still online after wiping the build environment.</p>\n\n\nNow you can re-build the version with a fresh build environment!\n",
+      "id": "wiping-a-build-environment",
+      "title": "Wiping a Build Environment"
+    }
+  ],
+  "path": "guides/wipe-environment"
 }