QA Tester Career Inside the Real Estate Industry, Explained

Test cases - Property search filters

TC01  Filter: 2 BHK, City: Noida
      Expected: only 2 BHK properties in Noida

TC02  Budget: 40 to 60 lakh
      Expected: no property outside the range

TC03  Sort by price: low to high
      Expected: each price <= next price

TC04  Combine filters: 3 BHK + Ready to move + Gurugram
      Expected: all three conditions true for every result

TC05  No matching results
      Expected: friendly "no properties found" message,
      option to clear filters

TC06  Clear all filters
      Expected: full listing returns

Negative and edge test cases

- Minimum budget greater than maximum budget
- Special characters in locality search: <script>
- Very long locality name (200+ characters)
- Search with network switched off (mobile)
- Rapidly changing filters while results load
- Property with no images uploaded
- Price shown as 0 or blank

Good testers spend as much time on these
as on the happy path.

# Automated check of an EMI calculator function
# Run: python test_emi.py   (or: pytest test_emi.py)

def emi(principal, annual_rate_pct, months):
    if annual_rate_pct == 0:
        return round(principal / months, 2)
    r = annual_rate_pct / 12 / 100
    factor = (1 + r) ** months
    return round(principal * r * factor / (factor - 1), 2)

def test_standard_case():
    # 1,00,000 at 12% for 12 months
    assert emi(100000, 12, 12) == 8884.88

def test_zero_interest():
    assert emi(120000, 0, 12) == 10000.0

def test_longer_tenure_lowers_emi():
    assert emi(5000000, 8.5, 240) < emi(5000000, 8.5, 120)

if __name__ == "__main__":
    test_standard_case()
    test_zero_interest()
    test_longer_tenure_lowers_emi()
    print("All EMI tests passed")

Site visit booking - scenarios

S1  Book an available slot -> confirmation shown + SMS/email sent
S2  Book a past date      -> blocked with clear message
S3  Two users, same slot  -> only one succeeds; other sees "slot taken"
S4  Cancel a booking      -> slot becomes available again
S5  Reschedule            -> old slot freed, new slot reserved
S6  Reminder              -> sent before the visit at the set time
S7  Agent dashboard       -> booking appears for the assigned agent

-- Verify listing data quality (SQLite / PostgreSQL)
CREATE TABLE listings (id INTEGER, city TEXT, bhk INTEGER, price_lakh REAL, status TEXT);
INSERT INTO listings VALUES
  (1, 'Noida', 2, 55.0, 'active'),
  (2, 'Noida', 3, NULL, 'active'),
  (3, 'Delhi', 2, 0, 'active'),
  (4, 'Gurugram', 4, 210.0, 'sold');

-- Active listings with missing or zero price = bugs to report
SELECT id, city, bhk, price_lakh
FROM listings
WHERE status = 'active' AND (price_lakh IS NULL OR price_lakh <= 0);

Bug ID: RE-142
Title: Budget filter shows properties above maximum budget
Environment: Web, Chrome latest, staging
Severity: High    Priority: High

Steps:
1. Open property search
2. Set city = Noida, budget = 40 to 60 lakh
3. Apply filter

Expected: all results priced 40-60 lakh
Actual: 3 results priced above 60 lakh (IDs 881, 902, 915)

Attachments: screenshot, network response
Notes: prices stored in rupees for these IDs, others in lakh?

Test Case Sheet

ID     Module     Scenario                     Steps   Expected        Status
TC01   Search     2 BHK filter in Noida        ___     Only 2 BHK      Pass/Fail
TC02   EMI        12% for 12 months            ___     8884.88         Pass/Fail
TC03   Booking    Book available slot          ___     Confirmation    Pass/Fail
TC04   Lead form  Submit with invalid phone    ___     Error message   Pass/Fail

Bug Report Template

Bug ID: _____
Title (what is wrong, where): _______________
Environment: web / Android / iOS, version: ___
Severity: Critical / High / Medium / Low
Steps to reproduce:
1. ___
2. ___
Expected result: _______________
Actual result: _______________
Evidence: screenshot / video / logs

Release Checklist (property app)

[ ] Search and filters regression passed
[ ] EMI calculator checks passed
[ ] Booking and cancellation flows passed
[ ] Lead forms reach the CRM
[ ] Payments tested in sandbox mode
[ ] Mobile and desktop layouts checked
[ ] No open critical or high bugs
[ ] Sign-off from product owner