Why Companies in Delhi Choose Uncodemy for Software Testing

# Prioritise test areas by likelihood x impact (1-5 each); example values
areas = {
    "payment":        (3, 5),
    "login":          (2, 5),
    "search":         (3, 3),
    "profile update": (2, 2),
    "help page":      (1, 1),
}
ranked = sorted(areas.items(), key=lambda a: a[1][0] * a[1][1], reverse=True)
for name, (likelihood, impact) in ranked:
    score = likelihood * impact
    level = "high" if score >= 10 else "medium" if score >= 5 else "low"
    print(f"{name:15} score {score:2}  {level}")

Area: payment (high risk)

Goals:
- Valid payment completes and order is saved
- Declined payment shows a clear message; no order created
- Double-click on Pay does not charge twice
- Session timeout during payment is handled safely
- Amounts with decimals and large values are correct

Evidence: test cases, screenshots, SQL checks of saved orders

# pip install pytest-playwright && playwright install chromium
from playwright.sync_api import Page, expect

class LoginPage:
    def __init__(self, page: Page):
        self.page = page
        self.email = page.get_by_label("Email")
        self.password = page.get_by_label("Password")
        self.submit = page.get_by_role("button", name="Sign in")
        self.error = page.locator("#error")

    def login(self, email: str, password: str) -> None:
        self.email.fill(email)
        self.password.fill(password)
        self.submit.click()

HTML = """<label>Email <input></label><label>Password <input type=password></label>
<button onclick="document.getElementById('error').textContent='Invalid credentials'">Sign in</button>
<p id=error></p>"""

def test_wrong_password_shows_error(page: Page):
    page.set_content(HTML)
    LoginPage(page).login("user@example.com", "wrong")
    expect(page.locator("#error")).to_have_text("Invalid credentials")

# pip install requests pytest   Public practice API
import pytest
import requests

BASE = "https://jsonplaceholder.typicode.com"

@pytest.mark.parametrize("path,expected", [
    ("/posts/1", 200),
    ("/posts/999999", 404),
    ("/no-such-endpoint", 404),
])
def test_status_codes(path, expected):
    r = requests.get(BASE + path, timeout=10)
    assert r.status_code == expected

def test_post_shape():
    body = requests.get(f"{BASE}/posts/1", timeout=10).json()
    assert isinstance(body["id"], int) and body["title"]

# .github/workflows/qa.yml
name: qa
on: [push, pull_request]
jobs:
  tests:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with: { python-version: "3.12" }
      - run: pip install -r requirements.txt pytest pytest-playwright pytest-html requests
      - run: python -m playwright install --with-deps chromium
      - run: pytest -q --html=report.html --self-contained-html
      - if: always()
        uses: actions/upload-artifact@v4
        with: { name: qa-report, path: report.html }

1. Which test design techniques are taught and practised?
2. Which automation tool and language are used?
3. Is API testing included with hands-on labs?
4. Do learners run tests in a CI pipeline?
5. How are flaky tests discussed and handled?
6. Can we see a sample learner project?
7. What are the current team options and fees in writing?

Team: ______________   Location: Delhi / NCR / remote
Application type: web / mobile / API
Current testing: mostly manual / some automation
Top gaps: test design / automation / API / CI
Goal: e.g., automated regression for core flows running on every PR
Format: classroom / online / hybrid
Success measure: suite in CI; regression time reduced; escaped defects tracked

Criteria             Uncodemy     Provider 2   Provider 3
Test design depth    ______       ______       ______
Automation project   ______       ______       ______
API testing labs     ______       ______       ______
CI practice          ______       ______       ______
Sample project seen  ______       ______       ______
Batch flexibility    ______       ______       ______
Fees in writing      ______       ______       ______

Review 4-6 weeks after training:

- Core flows automated: ____
- Tests running in CI: yes / no
- Flaky tests identified and fixed: ____
- Defects found earlier (examples): ______________
- Remaining gaps: ______________