What Happens When Two Software Tester Candidates Have Identical Resumes

PROJECT: E-commerce Website Testing

- Performed manual testing on the website
- Wrote test cases and executed them
- Logged bugs in Jira
- Performed regression testing
- Used Selenium for automation

SKILLS: Manual Testing, STLC, SDLC, Selenium,
Java, Jira, SQL, Agile, Postman

PROJECT: E-commerce Checkout Testing (training project)

- Tested checkout, coupons and refunds; focused on
  partial refunds across UPI, card and wallet
- Wrote 40 test cases incl. coupon stacking and
  GST rounding edge cases
- Logged 9 defects in Jira; 2 Major (coupon applied
  twice on refresh)
- Verified order and payment rows with SQL joins
- Automated 6 stable checkout flows (Selenium,
  Python, pytest)

SKILLS: same list as Candidate A

(Use only numbers that are true for your own work.)

tester-portfolio/
  README.md            what each file shows, in 5 lines
  test-plan.pdf        1 page: scope, out of scope, risks
  test-cases.xlsx      checkout module, 40 cases
  bugs/
    BUG-07-coupon-applied-twice.pdf
    BUG-09-gst-rounding.pdf
  sql/
    order_payment_checks.sql
  automation/
    tests/test_checkout.py
    pages/checkout_page.py
    requirements.txt

Keep it small. Two excellent bug reports beat
twenty average ones.

# pytest + Selenium 4 (Python)
import os
import pytest
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

BASE = os.environ["APP_URL"]  # your local practice app

@pytest.fixture
def driver():
    d = webdriver.Chrome()
    yield d
    d.quit()

def test_coupon_cannot_apply_twice(driver):
    driver.get(BASE + "/cart?demo=1")
    wait = WebDriverWait(driver, 10)
    for _ in range(2):
        driver.find_element(By.ID, "coupon").clear()
        driver.find_element(By.ID, "coupon").send_keys("SAVE10")
        driver.find_element(By.ID, "apply").click()
    msg = wait.until(EC.visibility_of_element_located((By.ID, "coupon-msg")))
    assert "already applied" in msg.text.lower()
    assert driver.find_element(By.ID, "discount").text == "Rs 10"

STORY SHOP-212: Cancel order

As a customer, I want to cancel my order before it
ships, so that I am not charged for items I no
longer want.

Acceptance criteria:
AC1  Cancel button is visible only while status is
     'Placed' or 'Packed'.
AC2  Cancellation is allowed within 24 hours of
     placing the order.
AC3  On cancel, status changes to 'Cancelled' and the
     customer gets an email.
AC4  Prepaid orders are refunded to the original
     payment method.

TC1 (AC1) Status Placed  -> Cancel visible
TC2 (AC1) Status Packed  -> Cancel visible
TC3 (AC1) Status Shipped -> Cancel hidden; API call
          to cancel also rejected
TC4 (AC2) Cancel at 23h 59m -> allowed
TC5 (AC2) Cancel at 24h 01m -> blocked with message
TC6 (AC3) After cancel: status Cancelled, one email,
          correct order ID in email
TC7 (AC4) UPI prepaid -> refund to same UPI
TC8 (AC4) COD order -> no refund triggered
TC9 (neg) Double-click Cancel -> only one cancellation
          and one email

Gaps to raise:
- Partly shipped order: can unshipped items be cancelled?
- Refund timeline and coupon handling are not defined
- Is exactly 24h 00m allowed or blocked?

FOR EACH PROJECT BULLET

Old bullet: ______________________________

Answer these:
  Which module or feature exactly? ______
  Which business rule did I test? _______
  How many cases (true number)? _________
  Best real defect found? _______________
  How did I verify (UI/API/SQL)? ________

New bullet (one line, 20 words or fewer):
  _________________________________________

Check: could another candidate write this exact
line? If yes, make it more specific.

PROOF-OF-WORK FOLDER

[ ] One-page test plan with scope and risks
[ ] Test case sheet with data and expected results
[ ] Two strong bug reports with evidence
[ ] Three SQL validation queries with comments
[ ] Small automation repo with assertions
[ ] README explaining what each file shows
[ ] All personal or real data removed
[ ] Opens quickly for screen sharing

LIVE TASK DRILL (10 minutes each)

Write a user story with 3-4 acceptance criteria for:
  - Changing a delivery address
  - Applying a referral code at sign-up
  - Rescheduling a doctor appointment
  - Downloading a monthly bank statement

Then, in 10 minutes:
  1. At least one test per criterion
  2. Boundary values where time or amount appears
  3. One negative or double-action case
  4. Two gaps or questions about the story
  5. A one-line priority note

Explain it aloud in 2 minutes.