---
schema_version: "1"
id: 78a478cddaa0993ea801a913ae053c77c263161af7a332f0eaa4ba4af8e73525
title: ApexGuru Test Case Antipatterns
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/apexguru_test_case_antipatterns.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.apexguru_test_case_antipatterns.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b210396a661b1f16e6db4f58ed62c8557532f44d5957a8a4eb31c6a089516f19
description: The test cases highlighted in ApexGuru help you find places in your Apex test code that aren’t valid, maintainable, or production-ready.
products:
  - Cross Cloud
release: "264"
---
# ApexGuru Test Case Antipatterns

The test cases highlighted in ApexGuru help you find places in your Apex test code that aren’t valid, maintainable, or production-ready.

- **[ApexGuru Test Case Antipattern: Using the testMethod Keyword](https://help.salesforce.com/s/articleView?id=xcloud.apexguru_test_case_antipattern_using_testmethod.htm&release=264.0.0&type=5)**  
    The testMethod syntax is outdated. Avoid using it to preserve confidence in your test suite and deployment quality.
- **[ApexGuru Test Case Antipattern: Writing Filler Statements](https://help.salesforce.com/s/articleView?id=xcloud.apexguru_test_case_antipattern_filler_statements.htm&release=264.0.0&type=5)**  
    Using meaningless code to inflate test coverage undermines code quality. Filler statements cause technical debt, missed bugs, and false code confidence. Focus on quality over quantity. Write meaningful tests for actual business logic and use coverage as a guide, not the goal.