2.0.0

.eslintrc.js

@@ -0,0 +1,57 @@
+module.exports = {
+    "env": {
+        "es6": true,
+        "node": true
+    },
+    "parser": "@typescript-eslint/parser",
+    "parserOptions": {
+        "project": "tsconfig.json",
+        "sourceType": "module"
+    },
+    "plugins": [
+        "@typescript-eslint"
+    ],
+    "rules": {
+        "@typescript-eslint/class-name-casing": "error",
+        "@typescript-eslint/indent": [
+            "error",
+            "tab"
+        ],
+        "@typescript-eslint/member-delimiter-style": [
+            "error",
+            {
+                "multiline": {
+                    "delimiter": "semi",
+                    "requireLast": true
+                },
+                "singleline": {
+                    "delimiter": "semi",
+                    "requireLast": false
+                }
+            }
+        ],
+        "@typescript-eslint/no-for-in-array": "error",
+        "@typescript-eslint/semi": [
+            "error",
+            "always"
+        ],
+        "constructor-super": "error",
+        "curly": "error",
+        "eqeqeq": [
+            "error",
+            "always"
+        ],
+        "no-caller": "error",
+        "no-debugger": "error",
+        "no-duplicate-case": "error",
+        "no-eval": "error",
+        "no-new-wrappers": "error",
+        "no-redeclare": "error",
+        "no-sparse-arrays": "error",
+        "no-throw-literal": "error",
+        "no-unsafe-finally": "error",
+        "no-unused-expressions": "error",
+        "no-unused-labels": "error",
+        "no-var": "error",
+    }
+};

.gitignore

@@ -2,5 +2,4 @@ out
 node_modules
 .vscode
 *.vsix
-*.tgz
-package-lock.json
+*.tgz

CHANGELOG.md

@@ -0,0 +1,11 @@
+# Change Log
+
+## 2.0.0 (Nov 28)
+	- Included classes from WSDL2Rest project UI tests utils
+	- Rename some of existing classes, and reorginize .ts file structure
+	- Update 'vscode-extension-tester' dependency to 2.1.1 version
+	- Migrate to eslint from deprecated tslint
+	- Include 'package-lock.json' to git repository
+	- Added 'dev' npm script option to package.json
+	- Updated README.md file
+	- Added CHANGELOG.md file into project to start tracking version changes

README.md

@@ -1,35 +1,36 @@
 [![npm version](https://badge.fury.io/js/vscode-uitests-tooling.svg?style=flat)](https://badge.fury.io/js/vscode-uitests-tooling) [![contributions welcome](https://img.shields.io/badge/contributions-welcome-brightgreen.svg?style=flat)](https://github.com/djelinek/vscode-uitests-tooling/issues) [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg?style=flat)](https://github.com/djelinek/vscode-uitests-tooling/blob/master/LICENSE)
 
 # vscode-uitests-tooling
-UI Tests Tooling for VS Code extensions is a package built on [VS Code Extension Tester](https://github.com/jrichter1/vscode-extension-tester). It provides more specific functions, wait conditions, sets of features and others for testing of VS Code extensions.
+UI Tests Tooling for VS Code extensions is a package built on [VS Code Extension Tester](https://github.com/redhat-developer/vscode-extension-tester). It provides more specific functions, wait conditions, sets of features and others for testing of VS Code extensions.
 
 ## Usage
 First simply install _vscode-extension-tester_ into your extension devDependencies:
 
 ```
-npm install -D vscode-extension-tester
+> npm install -D vscode-extension-tester
 ```
 
 Then install _vscode-uitests-tooling_ into your extension devDependencies:
 
 ```
-npm install -D vscode-uitests-tooling
+> npm install -D vscode-uitests-tooling
 ```
 
-After that just setup ui-test run script and thats all. (see [Test setup](https://github.com/jrichter1/vscode-extension-tester/wiki/Test-Setup)).
+After that just setup ui-test run script and thats all. (see [Test setup](https://github.com/redhat-developer/vscode-extension-tester/wiki/Test-Setup)).
 
 ## Contribution
 If you want to provide any new functionality, please create Issue or PR to this repository.
 
 ### Local development steps
-These are necessary steps for local contribution and testing of _vscode-uitests-tooling_ package. The 'npm pack' step is very important, because of peerDependency on _vscode-extension-tester_.
+These are necessary steps for local contribution and testing of _vscode-uitests-tooling_ package. The ```npm pack``` step is very important, because of peerDependency on _vscode-extension-tester_.
 
-vscode-uitests-tooling
-1. npm run clean
-2. npm install
-3. npm run compile
-4. npm pack
+##### Inside _vscode-uitests-tooling_ package run
+```
+> npm run dev
+```
 
-tested extension
-1. rm -rf _node_modules/_ _package-lock.json_
-2. npm install -D _file:../vscode-uitests-tooling/vscode-uitests-tooling-1.0.0.tgz_
+##### Inside developed extension run
+```
+> npm uninstall -D vscode-uitests-tooling
+> npm install -D file:../vscode-uitests-tooling/vscode-uitests-tooling-2.0.0.tgz
+```