Surviving Your First Week with Zero Knowledge Transfer

✓ Access checklist:
  - [ ] GitHub/GitLab repository access (all relevant repos)
  - [ ] JIRA/issue tracker access
  - [ ] Slack/Teams channels (dev, QA, operations)
  - [ ] VPN and internal network access
  - [ ] Test environment URLs and credentials
  - [ ] CI/CD dashboard access (Jenkins, GitHub Actions)
  - [ ] Database access (read-only initially)
  - [ ] Monitoring tools (Grafana, Datadog, logs)
  - [ ] Shared documentation (Confluence, Notion, Google Drive)

# Clone main application repo
git clone https://github.com/company/shopping-platform.git
cd shopping-platform
 
# Check the README
cat README.md
 
# Look for test directories
find . -name "*test*" -type d
find . -name "*spec*" -type d
 
# Count test files
find . -name "*Test.java" | wc -l
find . -name "*.spec.js" | wc -l

# Find test frameworks being used
grep -r "import.*junit" .
grep -r "describe\|it\(" . --include="*.js"
grep -r "RestAssured" . --include="*.java"
 
# Find configuration files
find . -name "*.xml" -name "*test*"
find . -name "testng.xml"
find . -name "jest.config.js"

// Example: ProductServiceTest.java
// This tells you what the ProductService does and how it's tested
@Test
public void testGetProductById() {
    Product product = productService.getById("SKU-123");
    assertNotNull(product);
    assertEquals("Laptop", product.getName());
}
// ☝️ Learning: There's a ProductService with a getById method
//    It returns Product objects with names

git log --name-only --since="6 months ago" -- "*Test.java" | grep Test.java | sort | uniq

# Java project example
mvn clean install    # Might take 10-30 minutes first time
mvn test            # Run all tests
 
# Node.js project example
npm install
npm test
 
# Note any failures or errors - they're clues!

🔴 Build fails with missing dependencies
→ Check if you need to install databases, Redis, etc.
→ Ask team for Docker Compose setup
 
🔴 Tests fail due to configuration
→ Look for .env.example or config.example files
→ Ask for environment variable values
 
🔴 Tests fail randomly (flaky tests!)
→ Note which ones - this is valuable information
→ Rerun them to confirm flakiness
→ Document the flaky tests for later fixing
 
🔴 Hundreds of test failures
→ Don't panic! Tests might be outdated
→ Focus on understanding WHY they fail
→ Check git history: when did they last pass?

# QE Onboarding - [Your Name] - Week 1
 
## Repository Structure
- Main repo: shopping-platform (Java 11, Spring Boot)
- Frontend repo: shopping-ui (React, TypeScript)
- Test location: `/src/test/java/`
 
## Test Frameworks
- Backend: JUnit 5, RestAssured, Mockito
- Frontend: Jest, React Testing Library
- E2E: Selenium WebDriver (older), considering Playwright
 
## Current Test Status
- Total API tests: ~450
- Passing: 425 (94%)
- Flaky: 15 (need investigation)
- Failing: 10 (known issues, tickets exist)
 
## Test Data Strategy
- Uses test database: `test_shopping_db`
- Data reset before each test class
- Test users: test1@example.com - test50@example.com
 
## CI/CD Pipeline
- GitHub Actions for PR builds
- Jenkins for nightly regression
- Tests run in Docker containers
- Average pipeline time: 25 minutes
 
## Questions to Ask
1. Who owns the payment service? (Tests are missing)
2. What's the plan for flaky tests?
3. Can we upgrade Selenium tests to Playwright?

"Hey [Dev Name], I'm the new QE getting up to speed. 
Could I shadow you for 30 minutes while you test your feature? 
I want to understand how you verify your changes."

- Search: "test failed" or "flaky test" - shows reliability issues
- Search: "production bug" - shows what escapes to prod
- Filter: Bugs created in last 3 months - recent pain points
- Filter: "QA" label - tickets related to testing

// Before (flaky due to hardcoded wait)
Thread.sleep(2000); // 😱 Don't do this
clickSubmitButton();
 
// After (explicit wait for element)
WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));
wait.until(ExpectedConditions.elementToBeClickable(submitButton));
submitButton.click();

// Before
@Test
public void test1() {
    assertEquals(true, service.process("123", "xyz", 5));
}
 
// After
@Test
public void testProcessOrder_WithValidData_ReturnsSuccess() {
    // Arrange
    String orderId = "123";
    String userId = "xyz";
    int quantity = 5;
    
    // Act
    boolean result = service.process(orderId, userId, quantity);
    
    // Assert
    assertTrue(result, "Order processing should succeed with valid data");
}

@Test
public void testAddToCart_WithZeroQuantity_ShouldRejectRequest() {
    // Arrange
    CartRequest request = new CartRequest("SKU-123", 0);
    
    // Act & Assert
    assertThrows(InvalidQuantityException.class, () -> {
        cartService.addItem(request);
    });
}

Title: Fix flaky test in CheckoutServiceTest
 
Description:
Fixed flaky test `testCheckoutFlow` by replacing Thread.sleep 
with explicit WebDriverWait. Test now consistently passes.
 
Before: Failed 3/10 runs
After: Passed 20/20 runs
 
Related: JIRA-456 (Flaky test ticket)

┌─────────┐      ┌──────────┐      ┌─────────┐
│   UI    │─────→│   API    │─────→│ Service │
└─────────┘      │ Gateway  │      └─────────┘
                 └──────────┘            │
                      │                  ↓
                      ↓            ┌──────────┐
                 ┌─────────┐      │ Database │
                 │  Cache  │      └──────────┘
                 └─────────┘

@Test
public void testProductSearch_MultipleFilters() {
    // Test: Search laptops under $1000 with 5-star rating
    
    SearchRequest request = SearchRequest.builder()
        .keyword("laptop")
        .maxPrice(1000)
        .minRating(5)
        .build();
    
    SearchResponse response = productService.search(request);
    
    // Verify all results match criteria
    assertFalse(response.getProducts().isEmpty());
    response.getProducts().forEach(product -> {
        assertTrue(product.getName().toLowerCase().contains("laptop"));
        assertTrue(product.getPrice() <= 1000);
        assertTrue(product.getRating() >= 5);
    });
}

Week 2 Summary:
✅ Wrote 5 new tests for Product Search feature
✅ Fixed 2 flaky tests in CheckoutServiceTest  
✅ Documented test coverage gaps in Payment Service
⏳ Need: Access to production logs for debugging
📚 Learning: How our promotion pricing algorithm works

// When docs are missing, read tests:
@Test
public void testPricingRules() {
    // This test SHOWS how pricing works
    Price price = pricingService.calculate(
        basePrice: 100,
        discountPercent: 10,
        taxRate: 0.08
    );
    
    // Expected: (100 - 10%) + 8% tax = $97.20
    assertEquals(97.20, price.getFinalAmount());
}

# Find who last worked on a file
git log --follow --all -- path/to/ProductService.java
 
# See what changed recently
git log --since="1 month ago" --oneline
 
# Find commits related to testing
git log --grep="test" --oneline
 
# Who to ask about payment service?
git log -- src/payment/ --format="%an" | sort | uniq -c | sort -rn

# Search for context
Slack search: "payment service" in:qa-channel
Slack search: "flaky test" from:@tech-lead
Slack search: "test environment down"
 
# Find the right person to ask
Search who posts in #backend-dev
Look at channel descriptions for ownership
Check "pinned items" in channels

❌ Bad: "How does checkout work?"
✅ Good: "I'm testing the checkout flow. I see we call 3 APIs:
        inventory, pricing, and payment. Does inventory get 
        reserved before or after payment succeeds?"
 
❌ Bad: "Tests are failing, help!"
✅ Good: "CartServiceTest is failing with NullPointerException 
        on line 45. I see it's trying to call mockUser.getId() 
        but mockUser is null. Is this a test data setup issue?"
 
❌ Bad: "Where's the documentation?"
✅ Good: "I'm looking for API documentation for the Payment 
        Service. I checked Confluence but didn't find it. 
        Is there a different place to look, or should I read 
        the OpenAPI spec in the code?"

Week 1: Ran tests locally ✅
Week 2: Fixed first flaky test ✅
Week 3: Wrote first new test ✅
Week 4: Found a real bug in testing ✅
Week 5: Improved test coverage by 5% ✅

@Disabled("Flaky test, will fix later") // ⚠️ "Later" never comes