Merge pull request #309 from webreinvent/feature/update-common-issues-and-solutions

Feature -> Develop | Update Common Issues and Solutions

Author: themodernpk

content/9.testing/2.automation/1.common-issues-and-solutions.md

@@ -38,7 +38,7 @@ All the major issues related to the automation testing have been listed down bel
 
 ### 2. Error Message: "Details: session not created: This version of ChromeDriver only supports Chrome version"
 
-**Description**: This issue occures when the package: `appium-chromium-driver` is outdated. Due to this there is a mismatch in the chrome browser version and the package.
+**Description**: This issue occures when the package: `appium-chromium-driver` and `chromedriver` is outdated. Due to this there is a mismatch in the chrome browser version and the package.
 
 **Solution**:
 1. Open the terminal in your project.
@@ -47,11 +47,14 @@ All the major issues related to the automation testing have been listed down bel
     npm i appium-chromium-driver --save-dev
     ```
 2. Update the chrome browser to the latest version. Open **Chrome > Settings > About Chrome**
-3. Now excute the script by the running the commnd below:
+3. Now, open `package.json` file and locate `chromedriver` package.
+4. Update the package version with your chrome browser version. Eg. **139.0.0**
+5. Run `npm install`.
+6. Now excute the script by the running the command below:
     ```shell
     npm run wdio
     ```
-4. The issue should have been resolved.
+7. The issue should have been resolved.
 
 ### 3. Error Message: "The requested port may already be in use."
 
@@ -139,4 +142,122 @@ The solution for this issues have to be done in three steps:
     9. After setting the path, the environment variables should look something like this:
     <img src="/images/testing/java_home_path.png">
 
-After performing the steps mentioned above. The issue should have been fixed.
+After performing the steps mentioned above. The issue should have been fixed.
+
+### 7. Error while installing `wdio-chromedriver-service` on webdriverio project.
+
+**Description**: This error occurs due to webdriverio version. Latest webdriverio version doesn't support `wdio-chromedriver-service`.
+
+**Solution**: We need to downgrade the webdriverio version to solve this issue since the latest version: `9.19.1` doesn't support this module.
+
+1. Execute the command given below to downgrade webdriverio version to v8.0.0
+    ```shell
+    npm install [email protected] --save-dev
+    ```
+2. Now, execute the command given below to install `wdio-chromedriver-service` module:
+    ```shell
+    npm install wdio-chromedriver-service --save-dev
+    ```
+
+**Note:** With the latest webdriverio version: v9. `wdio-chromedriver-service` is no longer required. It automatically fetches the installed chrome version driver.
+
+### 8. Error Message: unknown server-side error: Appium Flutter driver not found
+
+**Description**: Happens when the `appium-flutter-driver` plugin isn’t installed.
+
+**Solution**: Follow the steps mentioned below:
+
+1. Open your system's terminal.
+2. Execute the command given below to install appium-flutter-driver plugin:
+   ```shell
+   appium plugin install --source=npm appium-flutter-driver
+   ```
+
+### 9. Error Message: "A new session could not be created" in Appium tests
+
+**Description**: Occurs when Appium cannot start a session because the desired capabilities are invalid or the device/emulator is not available.
+
+**Solution**: Follow the steps mentioned below:
+1. Check if emulator/device is running:
+   ```shell
+   adb devices
+   ```
+   Ensure your device is listed.
+2. Verify capabilities in `wdio.conf.js` or `wdio.env.js` file:
+   ```js
+    capabilities: [{
+        platformName: 'Android',
+        'appium:deviceName': 'emulator-5554',
+        'appium:platformVersion': '14',
+        'appium:automationName': 'UiAutomator2',
+        'appium:app': '/path/to/app.apk'
+    }]
+   ```
+3. Execute the tests again and check.
+
+### 10. Error Message: "Command not found: wdio"
+
+**Description:** Occurs when you try to run wdio but the CLI is not installed locally or globally.
+
+**Solutions:** Follow the steps mentioned below.
+1. Install CLI locally in the project:
+   ```shell
+   npm install @wdio/cli --save-dev
+   ```
+2. Run using npx:
+   ```shell
+   npx wdio run ./wdio.conf.js
+   ```
+### 11. Error Message: "Appium exited before startup"
+
+**Description:** Appium server crashes because of missing dependencies.
+
+**Solutions:** Follow the steps mentioned below.
+1. Reinstall Appium 2.x globally:
+   ```shell
+   npm install -g appium
+   ```
+2. Install required drivers (example for Android):
+   ```shell
+   appium driver install uiautomator2
+   ```
+   Example for iOS:
+   ```shell
+   appium driver install xcuitest
+   ```
+3. Retry running tests.
+   
+### 12. `npm install` command not working
+
+**Error:**
+```shell
+npm : File C:\Program Files\nodejs\npm.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see 
+about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
+At line:1 char:1
++ npm install
++ ~~~
+    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
+    + FullyQualifiedErrorId : UnauthorizedAccess
+
+Above error on vs code terminal when i execute npm install.
+```
+
+**Description:** On Windows, when you run npm install from the PowerShell terminal in VS Code, PowerShell tries to execute npm.ps1 (the wrapper script for npm). But your system’s execution policy doesn’t allow running PowerShell scripts
+
+**Solutions:** We need to change the PowerShell execution policy to fix this issue. Follow the steps mentioned below:
+1. Open PowerShell as Administrator.
+2. Execute the command given below:
+   ```shell
+   Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned
+   ```
+3. Restart VS Code and try again:
+   ```shell
+   npm install
+   ```
+
+This should fix the problem. However, if this doesn't work, we can change vscode terminal to Command Prompt instead of PowerShell.
+1. In VS Code, go to Terminal → New Terminal.
+2. Click the dropdown arrow (v) in the terminal tab → select Command Prompt.
+3. Run `npm install`.
+
+This also should fix the problem.