[PECO-AI] PECOBLR-3873: [databricks-jdbc] Clarify single-test command in CONTRIBUTING.md

[prathamesh-db]

PECO Agent Workflow (Partner Ecosystem)

Jira Ticket: https://databricks.atlassian.net/browse/PECOBLR-3873

Changes

Added a single-test documentation bullet to the ## Testing section of CONTRIBUTING.md. The new bullet immediately follows the existing WireMock integration-testing bullet and provides the Maven command for running a specific test method. No source code, test files, or changelog entries were modified, as this is a docs-only change (NO_CHANGELOG=true).

Test Cases Written

None — this is a documentation-only change.

---

Contribution Guidelines

Contributing to Databricks JDBC Driver

---

• Communication
• Contribution Workflow
• Development Environment Setup
• Debugging
• Testing
• Coding Style
• Sign Your Work

We happily welcome contributions to the Databricks JDBC Driver. We use GitHub Issues
to track community reported issues and GitHub Pull Requests for
accepting changes. We are excited to work with the open source communities in the many years to come to improve the JDBC Driver.

Communication

• Before starting work on a major feature, please reach out to us via GitHub, E-Mail, etc.
  We will make sure no one else is already working on it and ask you to open a GitHub issue.
• A "major feature" is defined as any change that is > 100 lines of code altered (not including tests), or changes any
  user-facing behavior.
• We will use the GitHub issue to discuss the feature and come to agreement.
• The GitHub review process for major features is also important so that organizations with write access can come to
  agreement on design.
• If it is appropriate to write a design document, the document must be hosted either in the GitHub tracking issue, or
  linked to from the issue and hosted in a world-readable location.
• Small patches and bug fixes don't need prior communication. If you have identified a bug and have ways to solve it,
  please create an issue or create a pull request.

Contribution Workflow

Code contributions—bug fixes, new development, test improvement—all follow a GitHub-centered workflow. To participate in
Databricks JDBC Driver development, set up a GitHub account. Then:

• Fork the repo. Go to the project repo page and use the Fork button. This will create a copy of the repo, under your
  username. (For more details on how to fork a repository see this guide.)

• Clone down the repo to your local system.

  git clone git@github.com:YOUR_USER_NAME/databricks-jdbc.git

• Create a new branch to hold your work.

  git checkout -b new-branch-name

• Work on your new code. Write tests and run the Spotless code formatting plugin. The Spotless plugin also runs
  automatically during the build process.

  mvn test
  mvn spotless:apply

• Commit your changes.

  git add -A
  
  git commit -s -m "Commit Message"

• Push your changes to your GitHub repo.

  git push origin branch-name

• Open a Pull Request (PR). Go to the original project repo on GitHub. There will be a message about your recently
  pushed branch, asking if you would like to open a pull request. Follow the prompts, compare across repositories, and
  submit the PR. This will email the committers. You may want to consider sending an email to the mailing list for more
  visibility. (For more details, see the GitHub guide on PRs.)

Maintainers and other contributors will review your PR. Please participate in the conversation, and try to make any
requested changes. Once the PR is approved, the code will be merged.

Additional git and GitHub resources:

Git documentation

Git development workflow

Resolving merge conflicts

Development Environment Setup

We recommend using IntelliJ to develop the Databricks JDBC Driver. You can download the community edition here.
Once you have IntelliJ installed, open the Databricks JDBC Driver project by selecting File -> Open and selecting the
databricks-jdbc folder. Ensure that you have the Maven plugin loaded.

• Git Hooks - To ensure commit quality and enforce project policies (such as with our new post-commit hook), you must install the git hooks contained in scripts/githooks.
  Please run the following command after cloning the repository:

    chmod +x ./scripts/setup-git-hooks.sh

    ./scripts/setup-git-hooks.sh

Debugging

The Databricks JDBC Driver uses both SLF4J and JUL
logging framework. By default, the driver uses the JUL logging framework. For more information on logging, refer to the
repository's README.md.

The easiest and recommended way to enable debug logging is via JDBC URL which will automatically use the JUL logging
framework. This will send the logs to the file pattern databricks_jdbc.log.%i under the specified LogPath.

jdbc:databricks:<host:port>/default;transportMode=https;ssl=1;AuthMech=3;httpPath=<http path>;LogPath=/Users/spiderman;LogLevel=debug

Note that when running the repository tests using maven or editor, logs will be printed to the console as per the
logging.properties in src/test/resources.

Testing

• All changes to the Databricks JDBC Driver should be covered by unit tests.
• New features should be covered by integration tests where applicable. These tests are supported by a custom JUnit
  extension built on WireMock, which helps simulate production-like environments while reducing
  reliance on live systems. This approach improves CI/CD efficiency. For more details on the testing framework, refer to
  the repository's README.md.

Coding Style

• We generally follow this Java Style Guide.

Developer Certificate of Origin

To contribute to this repository, you must sign off your commits to certify that you have the right to contribute the
code and that it complies with the open source license.

You can easily do this by adding a "Signed-off-by" line to your commit message to certify your compliance. Please use
your real name as pseudonymous/anonymous contributions are not accepted.

Signed-off-by: Holly Smith <holly.smith@email.com>
Use your real name (sorry, no pseudonyms or anonymous contributions.)

If you set your user.name and user.email git configs, you can sign your commit automatically with git commit -s:

git commit -s -m "Your commit message"

---

This PR was generated by PECO Agent Workflow. Please review before merging.