Update test case guidelines to include parent-child entity relationships and PsiClass member access

Author: xterao

.claude/guidelines/TEST_CASE_GUIDELINE.md

@@ -4,7 +4,7 @@ Follow the rules below when implementing test code.
 ## Code Inspection Functionality
 Implement tests for code inspection functionality using the following steps:
 
-### **Implementation of Test Case Classes**
+## Implementation of Test Case Classes
 - Implement test case classes in `@src/test/kotlin/org/domaframework/doma/intellij/inspection`.
 - Implement test cases for each subclass of **AbstractBaseJavaLocalInspectionTool**.
 - Name the test case class as `<InspectionToolName>InspectionTest`.
@@ -17,14 +17,31 @@ Implement tests for code inspection functionality using the following steps:
 Create the target Dao class or SQL file for inspection.
 Wrap the elements to be error-highlighted with the **<error>** tag and specify the error message to be displayed using the **descr** option.
 
-#### Test Data for Dao Classes
+**Test Data for Dao Classes**
 - Implement test data Dao classes in **Java**.
 - Annotate test data Dao classes with **@Dao**.
 - Place them under the appropriate subpackage in `@src/test/testData/src/main/java/doma/example/dao/inspection`.
 - Implement any other necessary classes as needed.
 
+**Entity Test Data**
+When creating test cases, prepare and verify the following Entity classes to test parent-child relationships:
+- Parent class annotated with @Entity
+- Subclass without @Entity annotation
+- Subclass annotated with @Entity
+
+Using the above, create the following test cases for features that use `PsiClass`:
+- Test cases using fields/methods defined in parent classes
+- Test cases using fields/methods defined in subclasses
+
+**Examples**
+- Test that bind variable definition inspection doesn't highlight errors when using fields defined in parent classes
+- Test that include/exclude option checking in DAO method annotations doesn't highlight errors when using fields defined in parent classes
+- Test that code completion shows fields/methods defined in parent classes as completion candidates
+
 #### Test Data for SQL Files
 - Create and place SQL files in a directory named after the corresponding Dao class under `@src/test/testData/src/main/resources/META-INF/doma/example/dao`.
+- When creating test cases for bind variables, prepare test data that checks instance field methods, static field methods, field methods of elements defined in loop directives, custom functions, and built-in functions.
+  For cases combining multiple variables, ensure comprehensive coverage of all variable combination patterns.
 
 ### Reference
 For actual implementation examples using Doma, refer to the [Doma GitHub repository](https://github.com/domaframework/doma/tree/master/integration-test-java/src/main/java/org/seasar/doma/it/dao).

CLAUDE.md

@@ -107,6 +107,19 @@ Feature Package
     └── AnAction subclass
 ```
 
+### Common
+
+**Accessing `PsiClass` Members**
+When retrieving fields and methods from `PsiClass`, use `allFields` and `allMethods` instead of `fields` and `methods`.
+This is necessary to include members defined in parent classes.
+
+Alternatively, you can use [PsiParentClass](src/main/kotlin/org/domaframework/doma/intellij/common/psi/PsiParentClass.kt)
+to achieve equivalent functionality with `findField()` and `findMethod()`.
+
+**Separating Complex Logic**
+Each feature requires implementing corresponding classes following the IntelliJ platform conventions.
+Complex logic should not be implemented directly in these corresponding classes but delegated to separate classes (Processors or Handlers).
+
 ### Actions
 Action functionality for navigating between DAO files and SQL files
 
@@ -171,6 +184,10 @@ Code inspection functionality for DAO methods and DOMA directives in SQL
   - [ValidationResult](src/main/kotlin/org/domaframework/doma/intellij/common/validation/result): Classes that provide error messages and highlights for code inspection results
     - **Class Naming Rules**: Use `ValidationResult` as a suffix. Name classes according to the message resources to be displayed
 
+**Coding Rule**
+For code inspection features, always implement `InspectionTool` and `Visitor` as separate classes.
+When the logic within `Visitor` becomes complex, implement separate Processor classes for main processing or Handler classes for error highlighting.
+
 ### Completion
 Code completion functionality for DOMA directive syntax in SQL
 - **[Feature Package](src/main/kotlin/org/domaframework/doma/intellij/contributor/sql)**