Updated MTA-511 TC (#147)

* Updated MTA 511 test case, and changed the expected plugin info, and added a new config variable i.e. "extension_path" in vscode_config.json

* ignore vscode_plugin_info.txt when checking end of file

.pre-commit-config.yaml

@@ -4,6 +4,7 @@ repos:
     hooks:
     -   id: trailing-whitespace
     -   id: end-of-file-fixer
+        exclude: src/data/vscode_plugin_info.txt
     -   id: check-docstring-first
     -   id: check-json
 -   repo: https://github.com/ambv/black

src/config/vscode_config.json

@@ -1,4 +1,5 @@
 {
   "ide_path": "/usr/bin/code",
-  "plugin_cache_path": "/home/midays/.mta/tooling/vscode"
+  "plugin_cache_path": "",
+  "extensions_path" : ""
 }

src/data/vscode_plugin_info.txt

@@ -1,46 +1,32 @@
-
 Migration Toolkit for Applications (MTA) - VSCode Extension
 Description
 VSCode extension for application migration and modernization using MTA.
-
 VSCode
 This extension is published here in the Microsoft Visual Studio Marketplace.
-
 Features
 This extension provides the ability to analyze, assess, and migrate source code from within VSCode and Eclipse Che.
-
 The look and feel of both VSCode and Eclipse Che are very similar; therefore, the functionality demonstrated below should be consistent between the two environments.
-
 Configuration Editor
 Use the configuration editor to setup the analysis.
-
 Jump to Code
 Jump to code containing identified migration issues.
-
 Issue Details
 View details about the migration issue.
-
 Report
 Use the generated reports to better understand and assess the migration efforts.
-
 Eclipse Che
 This extension is supported in Eclipse Che.
-
 To add this plugin to a Che workspace, open Che, navigate to the plugins tab, and search using the keyword migration.
-
 Requirements
 Java Platform, JRE version 11 with JAVA_HOME environment variable
 A minimum of 4 GB RAM; 8 GB recommended
 Tip: The cli can be installed from within VSCode once the extension has been installed.
-
 Extension Settings
 This extension contributes the following settings:
-
 cli.executable.path: The location of the cli.
 Build
+bash
 $ npm run compile
-
 =======
-
 License
-MIT
+MIT

src/tests/vscode/test_mta_511_plugin_info.py

@@ -2,19 +2,22 @@
 
 import pytest
 
+from src.utils.general import find_mta_directory
 from src.utils.general import read_file
 
 DATA_DIR = os.path.dirname(os.path.dirname(os.path.dirname(os.path.realpath(__file__)))) + "/data/"
 
 
 @pytest.mark.vscode
-def test_mta_511_plugin_info(setup_vscode):
+def test_mta_511_plugin_info(setup_vscode, vscode_config):
     # Automates Polarion MTA-511
-
     vscode = setup_vscode
     vscode.set_focus()
-    fetched_vscode_plugin_info = vscode.get_plugin_text()
-    expected_vscode_plugin_info = read_file(DATA_DIR + "vscode_plugin_info.txt").split("\n")
+
+    extensions_path = vscode_config["extensions_path"]
+    readme_path = os.path.join(find_mta_directory(extensions_path), "README.md")
+    fetched_vscode_plugin_info = vscode.get_plugin_details_text_from_file(readme_path)
+    expected_vscode_plugin_info = read_file(DATA_DIR + "vscode_plugin_info.txt")
     vscode.close_active_tab()
 
-    assert set(expected_vscode_plugin_info) == set(fetched_vscode_plugin_info)
+    assert expected_vscode_plugin_info == fetched_vscode_plugin_info