Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.jataka.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Enterprise DevSecOps Add-Ons

Jataka is not only an automated testing tool. It can also operate as an automated principal architect for your Salesforce repository by enforcing your internal engineering policies. To make Jataka adapt to your organization, use these Configuration-as-Code features:
  • .jatakaignore for smart noise filtering
  • jataka-rules.yml for semantic architecture policy enforcement

​
1) Smart Noise Filtering (.jatakaignore)

By default, Jataka analyzes every Salesforce file changed in a pull request. Use .jatakaignore to exclude files or folders such as mock classes, legacy modules, or non-actionable test helpers. Create .jatakaignore in the repository root (or .jataka/ignore) and define standard glob patterns: 
# .jatakaignore

# Ignore Apex test and mock classes
force-app/main/default/classes/**/*Test.cls
force-app/main/default/classes/**/*Mock.cls

# Ignore a specific data factory
force-app/main/default/classes/TestDataFactory.cls

# Ignore an entire legacy application area
force-app/main/default/legacy-app/**

​
Expected Behavior

  • On PR open, Jataka fetches changed files.
  • Jataka filters those files through .jatakaignore.
  • If only some files are ignored, Jataka continues with the remaining files.
  • If all files are ignored, Jataka skips review and generation to save CI resources.

​
2) Custom AI Architecture Policies (jataka-rules.yml)

Traditional static scanners mainly depend on pattern matching. Jataka applies semantic policy evaluation, so it can enforce architecture intent even when implementation details vary. Define project-specific rules in jataka-rules.yml (or .jataka/rules.yml): Jataka Rules Example Define rules for your project like this: 
# jataka-rules.yml
rules:
  - id: ban-hardcoded-ids
    severity: CRITICAL
    message: "COMPANY POLICY: You are not allowed to use hardcoded Salesforce IDs (e.g., 0018000000xyz) in Apex. You must query them dynamically."

  - id: restrict-financial-data-dml
    severity: CRITICAL
    message: "Direct DML operations (insert, update, delete) on Financial_Data__c are strictly prohibited. You must route all updates through the FinancialService.cls framework."

  - id: require-parallel-tests
    severity: HIGH
    message: "All Apex test classes must include @isTest(isParallel=true) to speed up our CI/CD pipeline deployments."
When these rules are active, Jataka validates every incoming PR against them. Jataka Rule Enforcement on PR Jataka will ensure that these rules are followed in the coming PRs by failing check runs for policy violations and blocking merges until issues are resolved.

​
Checklist for Lead Architects

  • Create .jatakaignore in the repository root to filter non-actionable files.
  • Create jataka-rules.yml in the repository root to codify non-negotiable architecture standards.
  • Ensure GitHub Actions triggers Jataka after deployment to your scratch org or target environment.
  • Open a test PR and confirm policy checks fail/pass as expected.