ApexIntermediatetestingcoverageunit-tests
Design Apex test strategy achieving meaningful coverage and quality
Real World Scenario
Org has 86% coverage but production bugs slip through because tests only assert `System.assert(true)`.
Expected Answer
• Assert business outcomes: field values, record counts, exception messages
• Use Test.loadData or @TestSetup for reusable baseline data
• Test bulk paths with 200 records minimum for trigger logic
• Mock HTTP callouts with StaticResource or HttpCalloutMock
• Negative tests for validation rules, security exceptions, governor limit boundaries
• Avoid SeeAllData=true except for unavoidable metadata dependencies
• CI gate on coverage per class changed, not just org aggregate
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Assert business outcomes: field values, record counts, exception messages Also consider: Use Test.loadData or @TestSetup for reusable baseline data In practice: Test bulk paths with 200 records minimum for trigger logic Balance speed of delivery with maintainability.
Architect Perspective
Coverage is compliance metric, not quality metric—architects require assertion standards in code review checklists.