Node JS vs Selenium: A Clear Comparison for Beginners

// A minimal Node.js HTTP server — no framework
import http from "node:http";

const server = http.createServer((req, res) => {
  res.writeHead(200, { "Content-Type": "application/json" });
  res.end(JSON.stringify({ status: "ok", time: new Date() }));
});

server.listen(3000, () => {
  console.log("Server running on http://localhost:3000");
});

// What this shows:
// - Node.js is a runtime for JavaScript on the server
// - You write JavaScript, not a new language
// - The "server" is just a JS file you run with: node server.js
// - No browser involved anywhere

// Express API — the most common Node.js use case
import express from "express";

const app = express();
app.use(express.json());

const users = [
  { id: 1, name: "Asha" },
  { id: 2, name: "Rohit" },
];

app.get("/users", (req, res) => {
  res.json(users);
});

app.post("/users", (req, res) => {
  const user = { id: users.length + 1, ...req.body };
  users.push(user);
  res.status(201).json(user);
});

app.listen(3000, () => console.log("API on port 3000"));

// What this shows:
// - Node.js is used to build web APIs
// - Express is a framework, Node.js is the runtime underneath
// - This is what most "Node.js developer" jobs expect
// - You test this with Postman or curl, not Selenium

// A CLI tool written in Node.js — no web server
import fs from "node:fs/promises";
import path from "node:path";

async function listLargeFiles(dir, minMB = 10) {
  const entries = await fs.readdir(dir, { withFileTypes: true });
  for (const entry of entries) {
    if (!entry.isFile()) continue;
    const full = path.join(dir, entry.name);
    const stat = await fs.stat(full);
    if (stat.size / (1024 * 1024) >= minMB) {
      console.log(`${entry.name}: ${(stat.size / 1024 / 1024).toFixed(1)} MB`);
    }
  }
}

listLargeFiles(process.argv[2] || ".");
// Run: node list-large.js ./downloads

// What this shows:
// - Node.js is not just for web servers
// - It replaces Python or Bash for many automation tasks
// - It uses the same JavaScript you already know from the browser

# Python + Selenium — the most common combination
from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC

driver = webdriver.Chrome()
driver.get("https://example.com/login")

# Fill the form
driver.find_element(By.ID, "email").send_keys("test@example.com")
driver.find_element(By.ID, "password").send_keys("password123")
driver.find_element(By.CSS_SELECTOR, "button[type=submit]").click()

# Wait for dashboard to load
WebDriverWait(driver, 10).until(
    EC.presence_of_element_located((By.CSS_SELECTOR, "h1.dashboard-title"))
)

assert "dashboard" in driver.current_url
driver.quit()

# What this shows:
# - Selenium is a testing tool, not a language
# - You write in Python (or Java, JS, C#, Ruby)
# - It controls a real browser
# - The browser is the target, not the tool

// JavaScript + Selenium (selenium-webdriver npm package)
// This is where Node.js and Selenium meet
const { Builder, By, until } = require("selenium-webdriver");

(async () => {
  const driver = await new Builder().forBrowser("chrome").build();
  try {
    await driver.get("https://example.com/login");

    await driver.findElement(By.id("email")).sendKeys("test@example.com");
    await driver.findElement(By.id("password")).sendKeys("password123");
    await driver.findElement(By.css("button[type=submit]")).click();

    await driver.wait(until.elementLocated(By.css("h1.dashboard-title")), 10000);
    const url = await driver.getCurrentUrl();
    if (!url.includes("dashboard")) throw new Error("Not on dashboard");

    console.log("Test passed");
  } finally {
    await driver.quit();
  }
})();

// Key point for beginners:
// Node.js runs the JavaScript
// Selenium controls the browser
// They work together — but they are not the same thing

// Modern alternative — Playwright (successor pattern to Selenium)
// Same idea: control a browser from code
const { chromium } = require("playwright");

(async () => {
  const browser = await chromium.launch();
  const page = await browser.newPage();

  await page.goto("https://example.com/login");
  await page.getByLabel("Email").fill("test@example.com");
  await page.getByLabel("Password").fill("password123");
  await page.getByRole("button", { name: /log in/i }).click();

  await page.waitForURL("**/dashboard");
  await browser.close();
  console.log("Test passed");
})();

// Note for beginners:
// - Playwright and Cypress are newer alternatives to Selenium
// - Learning Selenium first is still valuable — it is everywhere
// - But Playwright is now the modern default in new projects
// - Node.js is still the runtime for JS versions of all three

// Your Node.js app — a simple login API
// (this is what you are testing in the next tab)
import express from "express";

const app = express();
app.use(express.json());

const users = [{ email: "test@example.com", password: "pass123" }];

app.post("/login", (req, res) => {
  const { email, password } = req.body;
  const user = users.find(u => u.email === email && u.password === password);
  if (!user) return res.status(401).json({ error: "Invalid credentials" });
  res.json({ token: "abc123", email });
});

app.listen(4000, () => console.log("API on :4000"));

// Why this matters for a beginner:
// - This is a real backend role's daily work
// - It is the "thing" you will test with Selenium below
// - Understanding the app makes you a better tester
// - Building the app makes you a better developer

// Selenium test — for a frontend that uses the above API
// (Assume login.html posts to /login and shows #error on failure)
const { Builder, By, until } = require("selenium-webdriver");

(async () => {
  const driver = await new Builder().forBrowser("chrome").build();
  try {
    await driver.get("http://localhost:3000/login.html");

    // Happy path
    await driver.findElement(By.id("email")).sendKeys("test@example.com");
    await driver.findElement(By.id("password")).sendKeys("pass123");
    await driver.findElement(By.css("button[type=submit]")).click();
    await driver.wait(until.urlContains("/dashboard"), 5000);

    // Sad path
    await driver.get("http://localhost:3000/login.html");
    await driver.findElement(By.id("email")).sendKeys("wrong@example.com");
    await driver.findElement(By.id("password")).sendKeys("nope");
    await driver.findElement(By.css("button[type=submit]")).click();
    const err = await driver.wait(
      until.elementLocated(By.id("error")), 5000
    );
    const text = await err.getText();
    if (!text.includes("Invalid")) throw new Error("Expected error");

    console.log("Both tests passed");
  } finally {
    await driver.quit();
  }
})();

// Why this is impressive in interviews:
// - You built the app AND tested it
// - You understand both sides of the stack
// - This qualifies you for developer AND SDET roles
// - You wrote both in one language (JavaScript)