Category: Testing

Technical & Soft Skills Every QA Tester Should Master

🧠 Top Skills That Are Important for a Test Professional in 2025

Software testing has transformed rapidly with the rise of automation, agile, AI, and complex digital ecosystems. A test professional today is no longer limited to clicking through test cases—they are expected to be problem solvers, communicators, coders, and sometimes even data analysts.

The infographic below shows a breakdown of the most critical testing skills, based on industry-wide feedback.

📌 Why These Skills Matter

With constant software releases, test professionals need to ensure quality without slowing down development. That means:

  • Faster feedback loops
  • Deeper collaboration with developers
  • Testing beyond just functionality (security, usability, performance)
  • Understanding user behavior and business context

These skills help testers not just find bugs—but prevent them.

📊 Top Skills Breakdown

Here’s a detailed look at what each skill means and why it matters:

1. 🗣️ Communication Skills (75% Very Important)

📍 Why it’s critical:
Testers must clearly document bugs, write test cases, and explain defects to developers and stakeholders. Good communication prevents misunderstandings and keeps the team aligned.

2. ⚙️ Automation & Scripting (65%)

📍 Why it’s critical:
Manual testing can’t scale. Knowledge of automation frameworks like Selenium, Cypress, or Playwright is essential. Scripting in languages like Python, Java, or JavaScript can save hours of repetitive work.

3. 📚 General Testing Methodologies (62%)

📍 Why it’s critical:
Understanding black-box, white-box, regression, smoke, and exploratory testing helps testers select the right test at the right time.

4. 🌐 Web Technologies (60%)

📍 Why it’s critical:
Modern testers must understand HTML, CSS, and JavaScript to validate front-end issues or debug problems in browser-based apps.

5. 🔌 API Testing (55%)

📍 Why it’s critical:
More apps rely on microservices and APIs. Testers need tools like Postman, REST Assured, or Karate to test APIs for performance, reliability, and correctness.

6. 🛡️ Security Testing (48%)

📍 Why it’s critical:
Testers play a role in identifying vulnerabilities—such as XSS, injection attacks, or broken authentication—before attackers do.

7. 🔁 Agile Methodologies (45%)

📍 Why it’s critical:
Testers in Agile teams need to test early and often, work in sprints, and use practices like TDD (Test-Driven Development) and CI/CD pipelines.

8. 📈 Performance & Load Testing (42%)

📍 Why it’s critical:
Users expect fast apps. Testers use tools like JMeter, Gatling, or k6 to simulate thousands of users and ensure the app can handle peak loads.

9. 📱 Mobile Technologies (39%)

📍 Why it’s critical:
Testing on Android and iOS requires mobile-specific knowledge (e.g., gestures, screen sizes, emulators, Appium automation).

10. 🧠 Customer-Facing & Business Skills

📍 Why it’s critical:
Testers with empathy and business understanding catch real-world bugs—issues a user would actually care about.

🧩 Other Valuable (Emerging) Skills:

SkillUse Case
Data AnalysisUnderstanding logs, charts, trends for performance and issue tracking
Cloud TestingTesting apps deployed in AWS, Azure, GCP
Microservices TestingEnsuring independent services communicate reliably
Big Data TestingValidating high-volume, high-velocity data pipelines
IoT TestingTesting smart devices and networks
AI/ML TestingVerifying predictions, fairness, and performance of AI models
Operations ManagementCoordinating test environments, deployments, and reporting

Final Tips for Testers to Stay Relevant:

  1. 🧑‍💻 Practice automation daily – even if just small scripts
  2. 📚 Read about new tools and trends in QA weekly
  3. 🧪 Participate in real-world testing challenges (e.g., Bug Bashes, uTest)
  4. 🤝 Collaborate with developers and product owners
  5. 📊 Learn to report insights, not just bugs

Types of Software Testing Every QA Engineer Should Know

Software Testing is the process of evaluating a software application to ensure it works as expected, is secure, and performs well. It is broadly categorized into Static Testing and Dynamic Testing.

🔍 1. Static Testing

  • What it is:
    Testing the software without executing code. It’s done during the early stages of development.
  • Key methods:
    • Review
    • Walkthrough
    • Inspection

This helps find early-stage errors in requirements or design.

⚙️ 2. Dynamic Testing

  • What it is:
    Involves running the actual software and validating its behavior.
  • Two major branches: Functional & Non-Functional Testing

🔧 Functional Testing

Focuses on what the software does (its features and functions). It includes:

✅ White Box Testing

Tests internal code and logic. Done by developers.

  • Unit Testing – Tests individual functions/methods
  • Code/Statement/Path Testing – Analyzes code coverage
  • Branch Coverage – Ensures each decision point (like if-else) is tested

✅ Black Box Testing

Focuses on inputs and outputs without knowing the internal code.

  • Integration Testing – Checks interactions between modules
  • Smoke/Sanity Testing – Basic checks after builds
  • Functionality Testing – Verifies features as per requirements
  • Regression Testing – Ensures old features work after changes
  • System Testing – Full end-to-end testing of the entire app
  • User Acceptance Testing (UAT) – Final testing by users before release

🧱 Non-Functional Testing

Tests how the software performs rather than what it does. Examples:

  • Load and Stress Testing – Tests system behavior under high load
  • Compatibility Testing – Ensures software works on different devices and platforms
  • Security Testing – Checks for vulnerabilities and data protection
  • Recovery Testing – Verifies how the app recovers from crashes
  • Usability Testing – Ensures app is user-friendly
  • Cookies Testing – Validates cookie creation, expiry, and behavior

✅ Final Thoughts

Using the right types of software testing helps teams build secure, fast, and high-quality software. Static and dynamic testing together cover both the visible functions and hidden logic of the system.

IoT Testing Explained: A Complete Guide for QA Engineers

IoT Testing (Internet of Things Testing) is the process of testing the functionality, security, performance, and compatibility of IoT devices and systems. As more smart devices get connected—like smartwatches, home sensors, connected cars, and industrial machines—IoT Testing ensures everything works smoothly and safely.

When IoT devices fail, it can lead to real-world problems like security breaches, system crashes, or poor customer experiences. That’s why proper testing is critical before launching any IoT product.

🔍 Why is IoT Testing Important?

Imagine a smart home system where the thermostat, security cameras, and lights are all connected. If even one device malfunctions, the whole system could fail. IoT Testing helps developers find and fix issues before they reach real users.

🧰 Types of IoT Testing (Explained Simply)

Here are the main types of IoT Testing you should know:

1. ✅ Usability Testing

What it does:
Checks if the IoT device is easy to use.
Example: Is the mobile app for a smart bulb simple to navigate?

2. 🧩 Compatibility Testing

What it does:
Makes sure the device works across different networks, platforms, and versions.
Example: Can a smart fridge connect with both Android and iOS apps?

3. ⚙️ Reliability & Scalability Testing

What it does:
Tests how stable the system is when more devices or users are added.
Example: Will a smart sensor network still work if 100 more sensors are added?

4. 🔐 Security Testing

What it does:
Validates if the system is safe from hackers and protects user data.
Example: Can unauthorized users access your smart door lock?

5. 📈 Performance Testing

What it does:
Checks how fast and responsive the devices are.
Example: Does the smart thermostat respond quickly when you change the temperature?

6. 📊 Data Integrity Testing

What it does:
Makes sure the data sent between devices is correct and uncorrupted.
Example: If a heart monitor sends data to a doctor’s dashboard, is that data accurate?

🚀 Final Thoughts

IoT Testing ensures that smart devices are reliable, secure, and user-friendly before reaching the market. It helps avoid costly failures and builds trust with users. Whether you’re testing a smart appliance, industrial sensor, or wearable device—these testing types are essential for success in the IoT world.

How to Use ExtentReports in .NET Selenium Automation Projects

Reports play a fundamental role when it comes to TESTING. Tester can now know the real-time reports of test suit execution. Reports made ease to know the ratio of Pass? Or Fail? Post-test suit execution and it is the only documentation to know about test execution results.

Everyone wish to see the detailed description of the test results. Don’t you? here is the solution for it. And, let us see how these reports can be achieved? in Selenium C# – NUnit framework automation testing.

To achieve detailed test execution results as HTML reports we need to rely on third party tool called => Extent Reports. These reports provide decent narration of test execution results and are depicted in PIE chart.

How to Reference Extent Reports in MS Visual Studio

Extent Reports can be directly referenced via NuGet Gallery:

Step 1) Project> Manage NuGet Packages

Step 2) In the next window

  1. Search for ExtentReports
  2. Select the search result
  3. Click Install

Step 3) Install selenium support from NuGet package

Step 3) Click ‘I Accept’

Step 4) Create a new C# class with the below code for Extent Reports. 

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

using OpenQA.Selenium;
using OpenQA.Selenium.Support.UI;
using OpenQA.Selenium.Chrome;

using NUnit.Framework;
using NUnit.Framework.Interfaces;
using NUnit;

using AventStack.ExtentReports.Reporter;
using AventStack.ExtentReports;
using System.IO;

namespace RnD
{
    [TestFixture]
    public class TestDemo1
    {
        public IWebDriver driver;

        public static ExtentTest test;
        public static ExtentReports extent;

        [SetUp]
        public void Initialize()
        {
            driver = new ChromeDriver();
        }


        [OneTimeSetUp]
        public void ExtentStart()
        {
            
            extent = new ExtentReports();
            var htmlreporter = new ExtentHtmlReporter(@"D:\ReportResults\Report" + DateTime.Now.ToString("_MMddyyyy_hhmmtt") + ".html");
            extent.AttachReporter(htmlreporter);

        }



        [Test]
        public void BrowserTest()
        {
            test = null;
            test = extent.CreateTest("T001").Info("Login Test");

            driver.Manage().Window.Maximize();
            driver.Navigate().GoToUrl("http://testing-ground.scraping.pro/login");
            test.Log(Status.Info, "Go to URL");

            //provide username
            driver.FindElement(By.Id("usr")).SendKeys("admin");
            //provide password
            driver.FindElement(By.Id("pwd")).SendKeys("12345");

            try
            {
                WebDriverWait wait = new WebDriverWait(driver, TimeSpan.FromSeconds(1));
                wait.Until(ExpectedConditions.ElementIsVisible(By.XPath("//h3[contains(.,'WELCOME :)')]")));
                //Test Result
                test.Log(Status.Pass, "Test Pass");

            }

            catch (Exception e)

            {
                test.Log(Status.Fail, "Test Fail");
                throw;

            }
        }

        [TearDown]
        public void closeBrowser()
        {
            driver.Close();
        }

        [OneTimeTearDown]
        public void ExtentClose()
        {
            extent.Flush();
        }
    }
}

Post running test method, the test execution report looks as shown below:

How to setup selenium webdriver with c#

Set Up Visual Studio with Selenium WebDriver:

Create a new project in Visual Studio:

Step 1) In the File Menu, Click New > Project

Step 2) In the next screen

  1. Select the option ‘Visual C#’
  2. Click on Console App (.Net Framework)
  3. Enter name as “RnD”
  4. Click OK

Step 3) The below screen will be displayed once the project is successfully created.

Set up Visual Studio with Selenium WebDriver:

Step 1) Navigate to Project-> Manage NuGet Packages

Step 2) In the next screen

  1. Search for Selenium on the resultant screen
  2. Select the first search result
  3. Click on ‘Install’

Step 3) The below message will be displayed once the package is successfully installed

Steps to install NUnit Framework:

Step 1) Navigate to Project-> Manage NuGet Packages

Step 2) In the next window

  1. Search for NUnit
  2. Select the search result
  3. Click Install

Step 3) The below message will appear once the installation is complete.

Steps to download NUnit Test Adapter

Please note that the below steps work only for 32-bit machines. For 64-bit machines, you need to download the ‘NUnit3 Test Adapter’ by following the same process as mentioned below.

Step 1) Navigate to Project-> Manage NuGet Packages

Step 2) In the next window

  1. Search NUnitTestAdapter
  2. Click Search Result
  3. Click Install

Step 3) Once install is done you will see the following message

Steps to download Chrome Driver

Step 1) Navigate to Project-> Manage NuGet Packages

Step 2) In the next window

  1. Search for Chromdriver
  2. Select the search result
  3. Click Install

Step 3) System may asked for permission. Click on ‘Yes to All’

Step 4) The below message will appear once the installation is complete.

Selenium and NUnit framework:

Selenium with NUnit framework allows differentiating between various test classes. NUnit also allows using annotations such as SetUp, Test, and TearDown to perform actions before and after running the test.

NUnit framework can be integrated with Selenium by creating a NUnit test class and running the test class using NUnit framework.

The below are the steps needed to create and run a test class using NUnit framework.

Steps to create a NUnit Test class in Selenium:

Step 1) In the Solution Explorer, Right clicked on project > Add > Class

Step 2) Class creation window will appear

  1. Provide a name to the class
  2. Click on Add button

Step 3) The below screen will appear.

Step 4) Add the following code to the created class. Please note that you need to specify the location of ‘chromdriver.exe’ file during chrome driver initialization. 

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

using OpenQA.Selenium;
using OpenQA.Selenium.Support.UI;
using OpenQA.Selenium.Chrome;


using NUnit.Framework;
using NUnit.Framework.Interfaces;
using NUnit;

namespace RnD
{
    [TestFixture]
    public class TestDemo1
    {
        public IWebDriver driver;

        [SetUp]
        public void Initialize()
        {
            driver = new ChromeDriver();
        }

        [Test]
        public void BrowserTest()
        {
            driver.Manage().Window.Maximize();
            driver.Navigate().GoToUrl("https://www.google.com/");
        }

        [TearDown]
        public void closeBrowser()
        {
            driver.Close();
        }
    }
}

Step 4) Click on ‘Build’ -> ‘Build Solution’ or keypress ‘Ctrl + Shift + B’

Step 5) Once the build is successful, we need to open the Test Explorer window. Click on Test -> Windows -> Test Explorer

Step 6) Test Explorer window opens with the list of available tests. Right-click on Test Explorer and select Run Selected Tests

Step 7) Selenium must open the browser with specified URL and close the browser. Test case status will be changed to ‘Pass’ on the Test Explorer window.

Database Testing Checklist

Database Testing

  • Synchronization between the database and the values displayed in our client/web.
  • Query results, views, stored procedures, indexers Etc.
  • Data manipulation (Update, Delete, insert Etc.).
  • Database performance.
  • Data maintenance.
  • Table’s structure.
  • Data recovery.
  • Data integrity.
  • Others

Clean database testing

  • Verify clean database testing.
  • Input 1st data

Database system-level tests

  • Validate the DB behavior of any case of service failures (recovery, error handling Etc.).
  • Validate that all indexes are created when it can increase the system performance.
  • Validate that appropriate events are created ad sent to the EventVwr/trace log.
  • Validate that DB tables are created with informative and reasonable names.
  • Try to work when the storage is ‘0’ and the e database is in running state.
  • Perform your tests on different versions (SQL 2005, 2008, 2012 etc.).
  • Validate the software security model (User roles, permissions etc.).
  • Validate the connection strings against SQL/Win authentications.
  • Validate data migrations (Different Database, Cluster, etc.).
  • Validate the behavior of the system against SQL injections.
  • Validate date to DB when the server is loaded.
  • Try to work when the database server is down.
  • Try to work with difference instance.
  • Validate restore and backup plans.

Database Integration Testing

  • Check that all columns are set with the relevant data type (Bigint, int, string Etc.)
  • Check that all data is logically organized in the relevant DB tables.
  • Check that each data item is located under the relevant column.
  • Is there any irrelevant data in the software dedicated tables?
  • Check that each table contains the relevant data.
  • Try to insert invalid database values.
  • Verify the data encryption (if any).

Data field tests

  • Validate that “Allow Null” condition is not allowed in a place that result a software failure.
  • Validate that all tables are created with logical structure (Primary, foreign keys.)
  • Validate that “Allow Null” condition is set when you need to allow it.
  • Validate that mandatory fields are created, this issue is very important when you work with multiple tables that depends on each other.

Procedure tests

  • Validate that the data the affected by the procedure is changed as expected.
  • Validate that all procedures are triggered when they supposed to run.
  • Validate that all the conditions receive an appropriate date inputs.
  • Validate that all procedures are created with the relevant code.
  • Is there an appropriate error handling for a failed procedure?
  • Validate that all the loops receive an appropriate date inputs.
  • Validate the procedure’s parameters (types, names, etc.).
  • Test the SP while executing the code manually.
  • Validate important code with SQL profiler.
  • Validate that all procedures names
  • Run tests with missing parameters.

Database and software integration (Client, web Etc.)

  • Validate that the user data is saved when the user “Apply” or “Submit” the changes.
  • Try to insert “NULL” values on fields that doesn’t supposed to receive it.
  • Validate that the user receives the current result when pulling data.
  • Validate that transaction the data type boundaries (Minima Etc.)
  • Validate that empty spaces are not committed to the database.
  • Validate that the values displayed based on the database data.
  • Try to insert UNICODE on Unicode character strings.
  • Try to insert values that exceed the field boundaries.
  • Validate that transactions the negative data values.
  • Insert invalid date format on Date and time fields.
  • Validate that the data integrity is not affected when the “Apply” or “Submit transactions are failing during the process.
  • Validate that the “Roll Back” option is available when the DB transaction is failed in the middle.

Data checking

  • Create Data from frontend and check by Query
  • Delete Data from frontend and check by Query

Complete Mobile Testing Checklist for Android and iOS Apps

Platform

  • Check OS depend on test
  • Check many OS’s we will support (Android / iOS / Windows Phone)?
  • What mobile / tablet device will be used?
  • What mobile / tablet screen size (Inch: 10 / 8)?
  • What will be happened if OS updated?

Device-Specific Features

  • Content – Text size, Content adjustment, Responsive design
  • UI- Touchscreen gestures- swipe, zoom, pinch, multi-touch, shake
  • Pre-install software (Such as for export or import file)?
  • Check if battery down
  • Check making/Receiving voice calls while the app is running
  • Check memory utilise overflow
  • Check resuming App from the same point as left at the time of switching to another app
  • Check data will be saved (SD card / internal memory)
  • Check happened if memory (SD card / internal memory) full and try to export
  • Check in portrait / landscape mode?
  • Check application for empty / large database
  • Check screen off / screen saver off.
  • What are difference real device and emulator?
  • Check minimise app while loading shows

Connectivity and Network Issues

  • Check data connection will be used (Mobile operator / wifi)
  • Check if data connection loss while saving data
  • Check if data connection slow while saving data
  • Check both connection are open; Now, lost wifi connection what will be happen; Vice versa
  • Check both connection are open; Now, slow wifi connection what will be happen; Vice versa
  • Check shows error message if connection failed
  • Check app bandwidth consumption

User Experenice

User Experience

  • Check app logo
  • Check menu logo
  • Check list page are searchable
  • Check list page are sortable
  • Check list page are filterable
  • Check screen resolution?
  • Check how many columns will display in list / details page?
  • Check able to export from list page?
  • Check able to print from list/ details page?
  • Check able to create design custom forms details page?
  • Check able to fill up fields in details page?
  • Check able to click button in list /details page?
  • Check navigation across different screen
  • Check responsiveness of the App Logo and Name
  • Check easy navigation across different screens
  • Check responsiveness of drop down lists
  • Check prompt display of errors and warning messages
  • Check spelling, typo and grammar in all kind of messages and labels
  • Check inactive buttons and active buttons
  • Check date format or date picker
  • Check amount with rounding figure
  • Check currency format
  • Check text field format
  • Check number key pad when number text field
  • Check auto save available
  • Check delete feature
  • Check Custom name feature or behaviour
  • Check sent email from on screen
  • Check description field enough space to enter data
  • Check easy way to ‘collapse or expand’ all data
  • Check all select feature in list page
  • Check user profile settings
  • Check notification feature available (Such as if new project add, delete or modified notification)
  • Check app version

Data Testing

  • Data Sync issue (If data added from mobile app but not showing in web app. Vice versa)
  • API testing
  • Check image / document upload and limitation
  • Check document / image view feature
  • Check list page data count shows or not
  • Check server down time
  • Check xero/ other third party software data sync (if applicable)
  • Check CRUD operation
  • Check concurrency message
  • Check will data save offline mode
  • Check data create/update/delete in offline but what will be happened when its in online
  • Check previous data access cache

Security Testing

  • Check login credential attach with mobile fingerprint
  • Check ‘Remmber me’ feature in login
  • Check app sign out / Sign in feature
  • Check cache clear and run application again
  • Check user logged in but inactive / locked from admin
  • Check non admin user logged in what data s/he can access
  • Check customer’s data security
  • Check customer payment data security
  • Check network protocols security for running application
  • Check user security policy
  • Check one user can see another user data or information
  • Check antivirus related issue

Performance Issue

  • Check time taken to launch the application
  • Check application performance at times of peak load conditions and continual key pad entry
  • Check splash performance check and ensuring it remains on screen for less than 1~2 seconds
  • Check application performance in low device battery and charging conditions
  • Check Integration with the device and other applications without hampering performance
  • Check application install/uninstall successfully within the desired timeframe
  • Check displaying error messages and exits gracefully at times of low memory issues
  • Check app performance at the time of a Network problem and error alert prompts
  • Check application performance when the Network is back in action
  • Check memory Consumption
  • Check hardware Utilisation
  • Check app behaviour if app crashed
  • Check device performance
  • Check server performance
  • Check network performance
  • Check Install or update app feature
  • Check OS based app limitation

Feedback Feature

  • Check ‘Contact Us’ feature
  • Check help guide available
  • Check legal feature available (Such as ‘Term and condition’ and ‘Privacy Policy’)

When You Skip QA: Why Testing Before Deployment Matters

Introduction

Have you ever heard the phrase “Don’t test in production”? Well, there’s a reason why tech teams take that seriously—because skipping Quality Assurance (QA) can lead to disasters. Imagine releasing a new app feature or website update and suddenly everything breaks. That’s what happens when we skip testing.

In this post, we’ll break down what QA means, why it’s important, and what could go wrong if you skip it — even for small changes.

What Is QA in Software?

Quality Assurance (QA) is the process of testing software before it reaches the end-users. The goal is to catch bugs, errors, or usability issues early so that customers never see them.

QA includes:

  • Functional Testing (Does it work as expected?)
  • Performance Testing (Is it fast and stable?)
  • Usability Testing (Is it easy to use?)
  • Security Testing (Is it safe from hackers?)

Why Skipping QA Is a Bad Idea

Let’s say a developer builds a feature and clicks “Deploy” without any testing. Everything seems fine at first… until:

  • 🔥 Servers crash under load
  • ❌ Users can’t log in
  • 🧾 Orders don’t go through
  • 📉 Customer trust is lost

In worst cases, companies lose money, users leave, or sensitive data leaks — all because someone skipped a few checks.

Real-Life Example

Let’s look at a simple scenario.

  1. A developer drinks coffee, feeling confident, and presses “Deploy” without testing.
  2. Within minutes, customers start complaining.
  3. Servers overheat, users panic, and the whole team scrambles to fix things.

All this could have been avoided with just one round of QA testing.

Easy Ways to Add QA to Your Workflow

Even if you’re a solo developer or part of a small team, here are simple ways to avoid disaster:

  1. ✅ Test Locally: Run the app on your computer and try different features.
  2. 🧪 Use Test Cases: Write down steps to test specific functions.
  3. 🧑‍🤝‍🧑 Get Peer Review: Ask a teammate to try the app before pushing.
  4. 🔁 Automated Testing: Use tools like Selenium, Playwright, or Jest to run tests automatically.
  5. 🌐 Have a Staging Environment: Test your app in a separate place that simulates production before going live.

The Takeaway

Skipping QA might feel like you’re saving time, but in the long run, it often leads to chaos, customer frustration, and emergency fixes. Just like you wouldn’t serve food without tasting it, don’t launch software without testing it.

So next time, before you press “Deploy,” ask yourself:
“Did I test this properly?”

Final Tip 🧠

If you’re just getting started, begin with manual testing — try using your app like a real user would. Over time, explore tools that automate repetitive tests. Even basic testing goes a long way!

How to setup selenium WebDriver with Nunit and Visual Studio (C#)

Selenium is an open source software tools which supporting tests automation. Now days, Software automation tools are becoming popular. Software automation tools are a time efficient. You will find different kinds of software automation tools, such as Load Runner, QTP, MS Test Manager, Jmeter etc. Selenium webdriver is a one of them. It is most popular automation tools.

 

Today, I am going to discussed about how to run selenium WebDriver with Nunit and Visual Studio (C#)

 

  • Download Nunit (http://www.nunit.org) and install in your system
  • Download selenium web-driver (http://docs.seleniumhq.org/download)
  • Open a new project and Create a Class Library
  • Add reference webdriver dll (selenium-dotnet-2.35.0 > net40) and nunit dll (Where you installed).

Webdriver dll

Nunit Dll

Or you can add Nunit dll from assemblies > Extension

  • When all of this is done and you can start write a code

Point 1:

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using System.Threading.Tasks;

using NUnit.Framework;

using OpenQA.Selenium;

using OpenQA.Selenium.Firefox;

using OpenQA.Selenium.Internal;

using OpenQA.Selenium.Support.UI;

 

Point 2:

namespace Automation

{
[TestFixture]
public class framework
{
private IWebDriver driver;
[SetUp]

public void LoadDriver()
{
Console.WriteLine("Check SetUp");
driver = new FirefoxDriver();
// To Maximise browser
 driver.Manage().Window.Maximize();
}

[Test]
public void Login()
{
driver.Navigate().GoToUrl("http://localhost/nopcommerce/login");
Console.WriteLine("Check URL");

// Type UserName
driver.FindElement(By.Id("Email")).SendKeys("admin@yourStore.com");

// Type Password
driver.FindElement(By.Id("Password")).SendKeys("admin");

// Clicked on Login Button
driver.FindElement(By.CssSelector("input.button-1.login-button")).Click();
}

[TearDown]
public void UnloadDriver()
{
Console.WriteLine("TearDown");
driver.Quit();
}
}
}

Above marked area. Just described how you will get id from login page

  • Build your application or press (Ctrl + Shift + B)
  • You have to run Nunit window to run this code.
  • Now, open a project from file menu and choose the project dll file or you can drag and drop the dll.
  • Click on ‘Run’ button to define result pass / fail