[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACH2BE3Z6R6S4FGPN5SN7W":3,"skill-same:01M6ACH2BE3Z6R6S4FGPN5SN7W":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6ACH2BE3Z6R6S4FGPN5SN7W","fineract-testing",null,"Choose, write, run and verify tests for Apache Fineract changes, covering JUnit unit tests, the fineract-provider Cucumber tests, Feign-client integration tests, the two-factor and OAuth2 suites, and Cucumber E2E scenarios. Use when adding or changing tests, when a code change needs test coverage, when a test fails, or before claiming that a change works.","apache\u002Ffineract","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACGYTY2VJZ9BH4K7MVTDM4",2625,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Ffineract\u002Fblob\u002Fdevelop\u002F.agents\u002Fskills\u002Ffineract-testing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,9,37,38,39,40,41,42],"fineract testing","testing","verify","changes","for","unit","factor","tests","provider","use","coverage","choose","e2e","code","run","unit tests","integration tests","change","test","2026-11-10 10:12:30",false,"---\nname: fineract-testing\ndescription: Choose, write, run and verify tests for Apache Fineract changes, covering JUnit unit tests, the fineract-provider Cucumber tests, Feign-client integration tests, the two-factor and OAuth2 suites, and Cucumber E2E scenarios. Use when adding or changing tests, when a code change needs test coverage, when a test fails, or before claiming that a change works.\n---\n\n# Fineract Testing\n\nPaths are relative to the repository root, and `.adoc` names refer to\n`fineract-doc\u002Fsrc\u002Fdocs\u002Fen\u002Fchapters\u002Ftesting\u002F`. Each rule below comes from the file or\ncheck named next to it; if this skill and that source disagree, the source wins.\n\n## Choose the suite\n\n| Suite | Where the tests live | Needs a running server | Guide |\n| --- | --- | --- | --- |\n| Unit | `src\u002Ftest\u002Fjava` of the module you changed | No | `CONTRIBUTING.md`, \"Unit tests\" |\n| Cucumber in `fineract-provider` | `fineract-provider\u002Fsrc\u002Ftest\u002Fresources\u002Ffeatures` | No | `.github\u002Fworkflows\u002Fbuild-cucumber.yml` |\n| Integration | `integration-tests` | Yes | `integration.adoc`, `integration-feign.adoc` |\n| Two-factor, OAuth2 | `twofactor-tests`, `oauth2-tests` | Yes, started in that auth mode | `integration.adoc`, \"Authentication modes\" |\n| Cucumber E2E | `fineract-e2e-tests-runner` (features), `fineract-e2e-tests-core` (steps) | Yes | `cucumber.adoc` |\n\nThe build never starts a server. Start one before running any suite marked \"Yes\",\nor every API call fails (`CONTRIBUTING.md`, \"How to run tests\").\n\n## Unit tests\n\n1. Use JUnit Jupiter, with Mockito through `@ExtendWith(MockitoExtension.class)`, as the\n   example in rule 2 does. The modules exclude the JUnit 4 vintage engine (for example\n   `fineract-provider\u002Fdependencies.gradle`), so a JUnit 4 `@Test` never runs.\n2. Code that reads the tenant or the business date needs the thread context. Set it in\n   `@BeforeEach` and clear it with `ThreadLocalContextUtil.reset()` in `@AfterEach`.\n   `Money` also needs the tenant's rounding mode, which sits in a static cache that\n   `reset()` does not clear: set it with `MoneyHelper.initializeTenantRoundingMode` and\n   remove it with `MoneyHelper.clearCacheForTenant`, as\n   `fineract-working-capital-loan\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Fportfolio\u002Fworkingcapitalloan\u002Fservice\u002FWorkingCapitalLoanAsOfBalanceReadServiceImplTest.java`\n   does.\n3. Let exceptions propagate instead of catching them. To test a failure, use\n   `assertThrows`, not `@Test(expected = ...)` (`CONTRIBUTING.md`, \"Error Handling\").\n4. Run one class with `.\u002Fgradlew :\u003Cmodule>:test --tests \u003CClassName>`. The command for the\n   whole fast suite is in `CONTRIBUTING.md`, \"Unit tests\". If you changed\n   `fineract-provider`, also run `.\u002Fgradlew :fineract-provider:cucumber`, because `test`\n   does not run its features.\n\n## Integration tests\n\nNew integration tests call the server through the generated Feign client. Read rules\nIT-01 to IT-20 in `integration-feign.adoc` before writing one.\n\n1. Extend the base class for the product under test: `FeignLoanTestBase`,\n   `FeignSavingsTestBase`, `FeignWorkingCapitalTestBase` or `FeignDepositTestBase` in\n   `integration-tests\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Fintegrationtests\u002Fclient\u002Ffeign\u002F`,\n   otherwise `FeignIntegrationTest` one directory up.\n2. The loan and savings bases register `LoanTestLifecycleExtension` and\n   `FeignSavingsLifecycleExtension`. Before and after every test, these close, un-approve\n   or reject every open loan or savings account in the tenant, so create accounts inside\n   each test, not in `@BeforeAll`.\n3. If your class needs its own `@BeforeAll`, give it a new name. Reusing the base\n   method's name (`setupHelpers`, `setupSavingsHelpers`, `setupWorkingCapitalHelpers`,\n   `setupDepositHelpers`) hides it, and the base helpers are never set up.\n4. Make calls through `FeignCalls` (`ok`, `executeVoid`, `fail`, `failVoid`) from\n   `fineract-client-feign\u002Fsrc\u002Fmain\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Fclient\u002Ffeign\u002Futil\u002FFeignCalls.java`,\n   and assert the exact status and error code of a failure (IT-02, IT-10).\n5. Never import `io.restassured`: the `FeignNoRestAssured` check in\n   `config\u002Fcheckstyle\u002Fcheckstyle.xml` fails the build, and REST Assured is no longer\n   on any test classpath.\n6. If the generated model lacks a field, add it to the matching `*ApiResourceSwagger`\n   class and regenerate both clients. Do not work around it in the test (IT-05,\n   \"Fixing a Generated Model at Source\").\n7. For anything that depends on the date, run the steps inside `runAt(date, ...)`. The\n   loan, savings and working capital bases provide it; elsewhere, call `runAt` on a\n   `FeignBusinessDateHelper`\n   (`integration-tests\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Fintegrationtests\u002Fclient\u002Ffeign\u002Fhelpers\u002FFeignBusinessDateHelper.java`).\n   It turns the business date on, sets it, and turns it off again afterwards.\n8. Keep each test class self-contained, and undo any global configuration you change.\n   CI splits test classes across shards on each of PostgreSQL, MySQL and MariaDB\n   (`.github\u002Fworkflows\u002Fbuild-postgresql.yml` and its MySQL and MariaDB variants), so no\n   class can rely on another one having run.\n\n## Keep the default lists in sync\n\nSome tests compare the database with a list kept by hand. When your change adds one\nof these, update the list in the same change:\n\n| When you add | Also update | Otherwise this fails |\n| --- | --- | --- |\n| A global configuration (`c_configuration` row) | `GlobalConfigurationHelper.getAllDefaultGlobalConfigurations()` in `integration-tests\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Fintegrationtests\u002Fcommon\u002FGlobalConfigurationHelper.java` | Tests that reset global configurations, such as `GlobalConfigurationTest` |\n| A scheduler job (`JobName` value) | Its `job` row, inserted by a Liquibase changeset | `SchedulerJobsTest`, which compares the two counts |\n| An external business event type | `ExternalEventConfigurationTestData` in `integration-tests\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Fintegrationtests\u002Fclient\u002Ffeign\u002Fmodules\u002F` | `ExternalEventConfigurationIntegrationTest` |\n\n## Cucumber E2E scenarios\n\n1. Put scenarios in a `.feature` file under\n   `fineract-e2e-tests-runner\u002Fsrc\u002Ftest\u002Fresources\u002Ffeatures` and step definitions under\n   `fineract-e2e-tests-core\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Ftest\u002Fstepdef`\n   (`cucumber.adoc`, \"Writing New E2E Tests\").\n2. On a fresh database, run once with `INITIALIZATION_ENABLED=true` to create the\n   products and charges the scenarios expect, and enable the business date\n   (`cucumber.adoc`, \"Test Data Initialization\" and \"Business Date Configuration\").\n3. From `fineract-e2e-tests-runner`, run one feature with\n   `..\u002Fgradlew cucumber -Pcucumber.features=\"src\u002Ftest\u002Fresources\u002Ffeatures\u002F\u003CName>.feature\"`,\n   and filter with `-Pcucumber.tags`. A filter that matches nothing reports\n   `0 scenarios` and still exits 0, so read the summary line (`integration.adoc`,\n   \"The WAR deployment\").\n4. Event assertions are skipped unless `EVENT_VERIFICATION_ENABLED=true`. E2E CI sets\n   it and runs ActiveMQ (`.github\u002Fworkflows\u002Fbuild-e2e-tests.yml`,\n   `docker-compose-postgresql-test-activemq.yml`), so a local run without it does not\n   check events.\n5. Use `@TestRailId:C\u003Cnumber>` only for an existing TestRail case, because results are\n   posted to that case\n   (`fineract-e2e-tests-core\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Ftest\u002Ftestrail\u002FTestRailClient.java`).\n   If there is none, ask in the PR rather than guessing.\n\n## Run and verify\n\n1. Start a server first. For the integration suites, use the Docker stack in\n   `CONTRIBUTING.md`, \"Integration tests\", which CI also uses; that section also covers\n   running without Docker. For E2E, see the previous section.\n2. Run the tests you added or changed against that server. Compiling and\n   `spotlessCheck` are not verification (IT-18).\n3. If a test fails, run it at the base commit before blaming your change (IT-20). If your\n   change touches server code, rebuild and restart the server at the base commit too.\n4. Check the report for skipped tests. Some `fineract-provider` tests are skipped, not\n   failed, when Docker is not running (`@Testcontainers(disabledWithoutDocker = true)`).\n5. If Gradle reports the test task as `UP-TO-DATE` or `FROM-CACHE`, the tests did not\n   run. Add `--rerun-tasks` (`CONTRIBUTING.md`, \"How to run tests\").\n6. Before pushing, run `.\u002Fgradlew spotlessApply` and the checks in\n   `.github\u002Fworkflows\u002Fbuild-quality-checks.yml` that your change touches (Checkstyle,\n   Spotless, SpotBugs, RAT, Javadoc).\n\n## Flaky tests\n\nFollow `CONTRIBUTING.md`, \"Pull Requests\". First rule out your own change (\"Run and\nverify\", step 3). Search JIRA for the test; if there is no report, file one and link it\nto FINERACT-850. Propose `@Disabled \u002F\u002F TODO FINERACT-NNNN` only when comments show the\ntest failing in at least 3 past PRs, and only in a separate PR.\n","# Fineract Testing\n\nPaths are relative to the repository root, and `.adoc` names refer to\n`fineract-doc\u002Fsrc\u002Fdocs\u002Fen\u002Fchapters\u002Ftesting\u002F`. Each rule below comes from the file or\ncheck named next to it; if this skill and that source disagree, the source wins.\n\n## Choose the suite\n\n| Suite | Where the tests live | Needs a running server | Guide |\n| --- | --- | --- | --- |\n| Unit | `src\u002Ftest\u002Fjava` of the module you changed | No | `CONTRIBUTING.md`, \"Unit tests\" |\n| Cucumber in `fineract-provider` | `fineract-provider\u002Fsrc\u002Ftest\u002Fresources\u002Ffeatures` | No | `.github\u002Fworkflows\u002Fbuild-cucumber.yml` |\n| Integration | `integration-tests` | Yes | `integration.adoc`, `integration-feign.adoc` |\n| Two-factor, OAuth2 | `twofactor-tests`, `oauth2-tests` | Yes, started in that auth mode | `integration.adoc`, \"Authentication modes\" |\n| Cucumber E2E | `fineract-e2e-tests-runner` (features), `fineract-e2e-tests-core` (steps) | Yes | `cucumber.adoc` |\n\nThe build never starts a server. Start one before running any suite marked \"Yes\",\nor every API call fails (`CONTRIBUTING.md`, \"How to run tests\").\n\n## Unit tests\n\n1. Use JUnit Jupiter, with Mockito through `@ExtendWith(MockitoExtension.class)`, as the\n   example in rule 2 does. The modules exclude the JUnit 4 vintage engine (for example\n   `fineract-provider\u002Fdependencies.gradle`), so a JUnit 4 `@Test` never runs.\n2. Code that reads the tenant or the business date needs the thread context. Set it in\n   `@BeforeEach` and clear it with `ThreadLocalContextUtil.reset()` in `@AfterEach`.\n   `Money` also needs the tenant's rounding mode, which sits in a static cache that\n   `reset()` does not clear: set it with `MoneyHelper.initializeTenantRoundingMode` and\n   remove it with `MoneyHelper.clearCacheForTenant`, as\n   `fineract-working-capital-loan\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Fportfolio\u002Fworkingcapitalloan\u002Fservice\u002FWorkingCapitalLoanAsOfBalanceReadServiceImplTest.java`\n   does.\n3. Let exceptions propagate instead of catching them. To test a failure, use\n   `assertThrows`, not `@Test(expected = ...)` (`CONTRIBUTING.md`, \"Error Handling\").\n4. Run one class with `.\u002Fgradlew :\u003Cmodule>:test --tests \u003CClassName>`. The command for the\n   whole fast suite is in `CONTRIBUTING.md`, \"Unit tests\". If you changed\n   `fineract-provider`, also run `.\u002Fgradlew :fineract-provider:cucumber`, because `test`\n   does not run its features.\n\n## Integration tests\n\nNew integration tests call the server through the generated Feign client. Read rules\nIT-01 to IT-20 in `integration-feign.adoc` before writing one.\n\n1. Extend the base class for the product under test: `FeignLoanTestBase`,\n   `FeignSavingsTestBase`, `FeignWorkingCapitalTestBase` or `FeignDepositTestBase` in\n   `integration-tests\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Fintegrationtests\u002Fclient\u002Ffeign\u002F`,\n   otherwise `FeignIntegrationTest` one directory up.\n2. The loan and savings bases register `LoanTestLifecycleExtension` and\n   `FeignSavingsLifecycleExtension`. Before and after every test, these close, un-approve\n   or reject every open loan or savings account in the tenant, so create accounts inside\n   each test, not in `@BeforeAll`.\n3. If your class needs its own `@BeforeAll`, give it a new name. Reusing the base\n   method's name (`setupHelpers`, `setupSavingsHelpers`, `setupWorkingCapitalHelpers`,\n   `setupDepositHelpers`) hides it, and the base helpers are never set up.\n4. Make calls through `FeignCalls` (`ok`, `executeVoid`, `fail`, `failVoid`) from\n   `fineract-client-feign\u002Fsrc\u002Fmain\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Fclient\u002Ffeign\u002Futil\u002FFeignCalls.java`,\n   and assert the exact status and error code of a failure (IT-02, IT-10).\n5. Never import `io.restassured`: the `FeignNoRestAssured` check in\n   `config\u002Fcheckstyle\u002Fcheckstyle.xml` fails the build, and REST Assured is no longer\n   on any test classpath.\n6. If the generated model lacks a field, add it to the matching `*ApiResourceSwagger`\n   class and regenerate both clients. Do not work around it in the test (IT-05,\n   \"Fixing a Generated Model at Source\").\n7. For anything that depends on the date, run the steps inside `runAt(date, ...)`. The\n   loan, savings and working capital bases provide it; elsewhere, call `runAt` on a\n   `FeignBusinessDateHelper`\n   (`integration-tests\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Fintegrationtests\u002Fclient\u002Ffeign\u002Fhelpers\u002FFeignBusinessDateHelper.java`).\n   It turns the business date on, sets it, and turns it off again afterwards.\n8. Keep each test class self-contained, and undo any global configuration you change.\n   CI splits test classes across shards on each of PostgreSQL, MySQL and MariaDB\n   (`.github\u002Fworkflows\u002Fbuild-postgresql.yml` and its MySQL and MariaDB variants), so no\n   class can rely on another one having run.\n\n## Keep the default lists in sync\n\nSome tests compare the database with a list kept by hand. When your change adds one\nof these, update the list in the same change:\n\n| When you add | Also update | Otherwise this fails |\n| --- | --- | --- |\n| A global configuration (`c_configuration` row) | `GlobalConfigurationHelper.getAllDefaultGlobalConfigurations()` in `integration-tests\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Fintegrationtests\u002Fcommon\u002FGlobalConfigurationHelper.java` | Tests that reset global configurations, such as `GlobalConfigurationTest` |\n| A scheduler job (`JobName` value) | Its `job` row, inserted by a Liquibase changeset | `SchedulerJobsTest`, which compares the two counts |\n| An external business event type | `ExternalEventConfigurationTestData` in `integration-tests\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Fintegrationtests\u002Fclient\u002Ffeign\u002Fmodules\u002F` | `ExternalEventConfigurationIntegrationTest` |\n\n## Cucumber E2E scenarios\n\n1. Put scenarios in a `.feature` file under\n   `fineract-e2e-tests-runner\u002Fsrc\u002Ftest\u002Fresources\u002Ffeatures` and step definitions under\n   `fineract-e2e-tests-core\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Ftest\u002Fstepdef`\n   (`cucumber.adoc`, \"Writing New E2E Tests\").\n2. On a fresh database, run once with `INITIALIZATION_ENABLED=true` to create the\n   products and charges the scenarios expect, and enable the business date\n   (`cucumber.adoc`, \"Test Data Initialization\" and \"Business Date Configuration\").\n3. From `fineract-e2e-tests-runner`, run one feature with\n   `..\u002Fgradlew cucumber -Pcucumber.features=\"src\u002Ftest\u002Fresources\u002Ffeatures\u002F\u003CName>.feature\"`,\n   and filter with `-Pcucumber.tags`. A filter that matches nothing reports\n   `0 scenarios` and still exits 0, so read the summary line (`integration.adoc`,\n   \"The WAR deployment\").\n4. Event assertions are skipped unless `EVENT_VERIFICATION_ENABLED=true`. E2E CI sets\n   it and runs ActiveMQ (`.github\u002Fworkflows\u002Fbuild-e2e-tests.yml`,\n   `docker-compose-postgresql-test-activemq.yml`), so a local run without it does not\n   check events.\n5. Use `@TestRailId:C\u003Cnumber>` only for an existing TestRail case, because results are\n   posted to that case\n   (`fineract-e2e-tests-core\u002Fsrc\u002Ftest\u002Fjava\u002Forg\u002Fapache\u002Ffineract\u002Ftest\u002Ftestrail\u002FTestRailClient.java`).\n   If there is none, ask in the PR rather than guessing.\n\n## Run and verify\n\n1. Start a server first. For the integration suites, use the Docker stack in\n   `CONTRIBUTING.md`, \"Integration tests\", which CI also uses; that section also covers\n   running without Docker. For E2E, see the previous section.\n2. Run the tests you added or changed against that server. Compiling and\n   `spotlessCheck` are not verification (IT-18).\n3. If a test fails, run it at the base commit before blaming your change (IT-20). If your\n   change touches server code, rebuild and restart the server at the base commit too.\n4. Check the report for skipped tests. Some `fineract-provider` tests are skipped, not\n   failed, when Docker is not running (`@Testcontainers(disabledWithoutDocker = true)`).\n5. If Gradle reports the test task as `UP-TO-DATE` or `FROM-CACHE`, the tests did not\n   run. Add `--rerun-tasks` (`CONTRIBUTING.md`, \"How to run tests\").\n6. Before pushing, run `.\u002Fgradlew spotlessApply` and the checks in\n   `.github\u002Fworkflows\u002Fbuild-quality-checks.yml` that your change touches (Checkstyle,\n   Spotless, SpotBugs, RAT, Javadoc).\n\n## Flaky tests\n\nFollow `CONTRIBUTING.md`, \"Pull Requests\". First rule out your own change (\"Run and\nverify\", step 3). Search JIRA for the test; if there is no report, file one and link it\nto FINERACT-850. Propose `@Disabled \u002F\u002F TODO FINERACT-NNNN` only when comments show the\ntest failing in at least 3 past PRs, and only in a separate PR.\n",{"name":5,"description":7},"develop","e048ee8b2b6a9f4a3b2dec2b79b4dd40ef480d99",".agents\u002Fskills\u002Ffineract-testing",2966,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ffineract","https:\u002F\u002Ffineract.apache.org","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-15 00:44:51",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add apache\u002Ffineract --skill fineract-testing",{"tool":63,"command":64},"bunx","bunx skills add apache\u002Ffineract --skill fineract-testing",{"tool":66,"command":67},"pnpm","pnpm dlx skills add apache\u002Ffineract --skill fineract-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Ffineract\u002Fblob\u002Fdevelop\u002F.agents\u002Fskills\u002Ffineract-testing\u002FSKILL.md",true,[],[72],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":81,"publishedAt":43},"01M6HEMQ9112PWPKS75JD5R6DW","fineract-database","Add or change Apache Fineract database schema and seed data with Liquibase, covering where a changelog part goes and how it is included, the PostgreSQL and MySQL contexts, the DDL safety, registration and backward-compatibility checks, seed rows such as permissions and configurations, and how Java code reaches the database. Use when adding or editing a Liquibase changelog, a table, column, index or seed row, a JPA relationship or a native SQL query, or when a database check fails in CI.","https:\u002F\u002Fgithub.com\u002Fapache\u002Ffineract\u002Fblob\u002Fdevelop\u002F.agents\u002Fskills\u002Ffineract-database\u002FSKILL.md",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[82,83,84,85,86,87,88,89,90,91,92,41,93,9,94,95,96,97,37,98],"fineract database","database","data","native","database schema","seed","relationship","query","compatibility","how","Safety","ci","postgresql","mysql","changelog","permissions","sql"]